website/static/docs/reference/generated/kubernetes-api/v1.32/index.html

54546 lines
5.5 MiB
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 lang="en">
<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-5.3.2.min.css" type="text/css">
<LINK rel="stylesheet" href="/css/fontawesome-4.7.0.min.css" type="text/css">
<LINK rel="stylesheet" href="/css/style_apiref.css" type="text/css">
</HEAD>
<BODY class="theme-auto">
<DIV id="wrapper" class="container-fluid">
<DIV class="row">
<DIV id="sidebar-wrapper" class="col-xs-4 col-sm-3 col-md-2 side-nav side-bar-nav">
<UL id="navigation">
<LI class="nav-level level-1" data-level="1">
<A href="#api-overview" class="nav-item">Overview</A>
</LI>
<LI class="nav-level level-1" data-level="1">
<A href="#api-groups" class="nav-item">API Groups</A>
</LI>
<LI class="nav-level level-1 has-children" data-level="1">
<A href="#workloads-apis" class="nav-item">Workloads APIs</A>
<UL id="workloads-apis-nav">
<LI class="nav-level level-2" data-level="2">
<A href="#container-v1-core" class="nav-item"><span class="gvk"><span class="k">Container</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#cronjob-v1-batch" class="nav-item"><span class="gvk"><span class="k">CronJob</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
<UL id="cronjob-v1-batch-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-cronjob-v1-batch" class="nav-item">Write Operations</A>
<UL id="write-operations-cronjob-v1-batch-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-cronjob-v1-batch" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-cronjob-v1-batch" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-cronjob-v1-batch" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-cronjob-v1-batch" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-cronjob-v1-batch" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-cronjob-v1-batch" class="nav-item">Read Operations</A>
<UL id="read-operations-cronjob-v1-batch-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-cronjob-v1-batch" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-cronjob-v1-batch" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-cronjob-v1-batch" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-cronjob-v1-batch" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-cronjob-v1-batch" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-cronjob-v1-batch" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-cronjob-v1-batch" class="nav-item">Status Operations</A>
<UL id="status-operations-cronjob-v1-batch-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-cronjob-v1-batch" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-cronjob-v1-batch" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-cronjob-v1-batch" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#daemonset-v1-apps" class="nav-item"><span class="gvk"><span class="k">DaemonSet</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
<UL id="daemonset-v1-apps-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-daemonset-v1-apps" class="nav-item">Write Operations</A>
<UL id="write-operations-daemonset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-daemonset-v1-apps" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-daemonset-v1-apps" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-daemonset-v1-apps" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-daemonset-v1-apps" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-daemonset-v1-apps" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-daemonset-v1-apps" class="nav-item">Read Operations</A>
<UL id="read-operations-daemonset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-daemonset-v1-apps" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-daemonset-v1-apps" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-daemonset-v1-apps" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-daemonset-v1-apps" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-daemonset-v1-apps" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-daemonset-v1-apps" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-daemonset-v1-apps" class="nav-item">Status Operations</A>
<UL id="status-operations-daemonset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-daemonset-v1-apps" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-daemonset-v1-apps" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-daemonset-v1-apps" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#deployment-v1-apps" class="nav-item"><span class="gvk"><span class="k">Deployment</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
<UL id="deployment-v1-apps-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-deployment-v1-apps" class="nav-item">Write Operations</A>
<UL id="write-operations-deployment-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-deployment-v1-apps" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-deployment-v1-apps" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-deployment-v1-apps" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-deployment-v1-apps" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-deployment-v1-apps" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-deployment-v1-apps" class="nav-item">Read Operations</A>
<UL id="read-operations-deployment-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-deployment-v1-apps" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-deployment-v1-apps" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-deployment-v1-apps" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-deployment-v1-apps" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-deployment-v1-apps" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-deployment-v1-apps" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-deployment-v1-apps" class="nav-item">Status Operations</A>
<UL id="status-operations-deployment-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-deployment-v1-apps" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-deployment-v1-apps" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-deployment-v1-apps" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#misc-operations-deployment-v1-apps" class="nav-item">Misc Operations</A>
<UL id="misc-operations-deployment-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-scale-deployment-v1-apps" class="nav-item">Read Scale</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-scale-deployment-v1-apps" class="nav-item">Replace Scale</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-scale-deployment-v1-apps" class="nav-item">Patch Scale</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#job-v1-batch" class="nav-item"><span class="gvk"><span class="k">Job</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
<UL id="job-v1-batch-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-job-v1-batch" class="nav-item">Write Operations</A>
<UL id="write-operations-job-v1-batch-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-job-v1-batch" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-job-v1-batch" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-job-v1-batch" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-job-v1-batch" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-job-v1-batch" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-job-v1-batch" class="nav-item">Read Operations</A>
<UL id="read-operations-job-v1-batch-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-job-v1-batch" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-job-v1-batch" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-job-v1-batch" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-job-v1-batch" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-job-v1-batch" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-job-v1-batch" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-job-v1-batch" class="nav-item">Status Operations</A>
<UL id="status-operations-job-v1-batch-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-job-v1-batch" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-job-v1-batch" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-job-v1-batch" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#pod-v1-core" class="nav-item"><span class="gvk"><span class="k">Pod</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="pod-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-pod-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-pod-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-pod-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#create-eviction-pod-v1-core" class="nav-item">Create Eviction</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-pod-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-pod-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-pod-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-pod-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-pod-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-pod-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-pod-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-pod-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-pod-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-pod-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-pod-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-pod-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-pod-v1-core" class="nav-item">Status Operations</A>
<UL id="status-operations-pod-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-pod-v1-core" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-pod-v1-core" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-pod-v1-core" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#resize-operations-pod-v1-core" class="nav-item">Resize Operations</A>
<UL id="resize-operations-pod-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-resize-pod-v1-core" class="nav-item">Read Resize</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-resize-pod-v1-core" class="nav-item">Patch Resize</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-resize-pod-v1-core" class="nav-item">Replace Resize</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#ephemeralcontainers-operations-pod-v1-core" class="nav-item">EphemeralContainers Operations</A>
<UL id="ephemeralcontainers-operations-pod-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-ephemeralcontainers-pod-v1-core" class="nav-item">Patch EphemeralContainers</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-ephemeralcontainers-pod-v1-core" class="nav-item">Read EphemeralContainers</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-ephemeralcontainers-pod-v1-core" class="nav-item">Replace EphemeralContainers</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#proxy-operations-pod-v1-core" class="nav-item">Proxy Operations</A>
<UL id="proxy-operations-pod-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-connect-portforward-pod-v1-core" class="nav-item">Create Connect Portforward</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#create-connect-proxy-pod-v1-core" class="nav-item">Create Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#create-connect-proxy-path-pod-v1-core" class="nav-item">Create Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-connect-proxy-pod-v1-core" class="nav-item">Delete Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-connect-proxy-path-pod-v1-core" class="nav-item">Delete Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#get-connect-portforward-pod-v1-core" class="nav-item">Get Connect Portforward</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#get-connect-proxy-pod-v1-core" class="nav-item">Get Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#get-connect-proxy-path-pod-v1-core" class="nav-item">Get Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#head-connect-proxy-pod-v1-core" class="nav-item">Head Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#head-connect-proxy-path-pod-v1-core" class="nav-item">Head Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-connect-proxy-pod-v1-core" class="nav-item">Replace Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-connect-proxy-path-pod-v1-core" class="nav-item">Replace Connect Proxy Path</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#misc-operations-pod-v1-core" class="nav-item">Misc Operations</A>
<UL id="misc-operations-pod-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-log-pod-v1-core" class="nav-item">Read Log</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#get-connect-exec-pod-v1-core" class="nav-item">Get Connect Exec</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#create-connect-exec-pod-v1-core" class="nav-item">Create Connect Exec</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#get-connect-attach-pod-v1-core" class="nav-item">Get Connect Attach</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#create-connect-attach-pod-v1-core" class="nav-item">Create Connect Attach</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#replicaset-v1-apps" class="nav-item"><span class="gvk"><span class="k">ReplicaSet</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
<UL id="replicaset-v1-apps-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-replicaset-v1-apps" class="nav-item">Write Operations</A>
<UL id="write-operations-replicaset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-replicaset-v1-apps" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-replicaset-v1-apps" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-replicaset-v1-apps" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-replicaset-v1-apps" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-replicaset-v1-apps" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-replicaset-v1-apps" class="nav-item">Read Operations</A>
<UL id="read-operations-replicaset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-replicaset-v1-apps" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-replicaset-v1-apps" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-replicaset-v1-apps" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-replicaset-v1-apps" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-replicaset-v1-apps" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-replicaset-v1-apps" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-replicaset-v1-apps" class="nav-item">Status Operations</A>
<UL id="status-operations-replicaset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-replicaset-v1-apps" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-replicaset-v1-apps" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-replicaset-v1-apps" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#misc-operations-replicaset-v1-apps" class="nav-item">Misc Operations</A>
<UL id="misc-operations-replicaset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-scale-replicaset-v1-apps" class="nav-item">Read Scale</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-scale-replicaset-v1-apps" class="nav-item">Replace Scale</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-scale-replicaset-v1-apps" class="nav-item">Patch Scale</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#replicationcontroller-v1-core" class="nav-item"><span class="gvk"><span class="k">ReplicationController</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="replicationcontroller-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-replicationcontroller-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-replicationcontroller-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-replicationcontroller-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-replicationcontroller-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-replicationcontroller-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-replicationcontroller-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-replicationcontroller-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-replicationcontroller-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-replicationcontroller-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-replicationcontroller-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-replicationcontroller-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-replicationcontroller-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-replicationcontroller-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-replicationcontroller-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-replicationcontroller-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-replicationcontroller-v1-core" class="nav-item">Status Operations</A>
<UL id="status-operations-replicationcontroller-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-replicationcontroller-v1-core" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-replicationcontroller-v1-core" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-replicationcontroller-v1-core" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#misc-operations-replicationcontroller-v1-core" class="nav-item">Misc Operations</A>
<UL id="misc-operations-replicationcontroller-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-scale-replicationcontroller-v1-core" class="nav-item">Read Scale</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-scale-replicationcontroller-v1-core" class="nav-item">Replace Scale</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-scale-replicationcontroller-v1-core" class="nav-item">Patch Scale</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#statefulset-v1-apps" class="nav-item"><span class="gvk"><span class="k">StatefulSet</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
<UL id="statefulset-v1-apps-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-statefulset-v1-apps" class="nav-item">Write Operations</A>
<UL id="write-operations-statefulset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-statefulset-v1-apps" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-statefulset-v1-apps" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-statefulset-v1-apps" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-statefulset-v1-apps" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-statefulset-v1-apps" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-statefulset-v1-apps" class="nav-item">Read Operations</A>
<UL id="read-operations-statefulset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-statefulset-v1-apps" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-statefulset-v1-apps" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-statefulset-v1-apps" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-statefulset-v1-apps" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-statefulset-v1-apps" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-statefulset-v1-apps" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-statefulset-v1-apps" class="nav-item">Status Operations</A>
<UL id="status-operations-statefulset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-statefulset-v1-apps" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-statefulset-v1-apps" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-statefulset-v1-apps" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#misc-operations-statefulset-v1-apps" class="nav-item">Misc Operations</A>
<UL id="misc-operations-statefulset-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-scale-statefulset-v1-apps" class="nav-item">Read Scale</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-scale-statefulset-v1-apps" class="nav-item">Replace Scale</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-scale-statefulset-v1-apps" class="nav-item">Patch Scale</A>
</LI>
</UL>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-1 has-children" data-level="1">
<A href="#service-apis" class="nav-item">Service APIs</A>
<UL id="service-apis-nav">
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#endpoints-v1-core" class="nav-item"><span class="gvk"><span class="k">Endpoints</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="endpoints-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-endpoints-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-endpoints-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-endpoints-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-endpoints-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-endpoints-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-endpoints-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-endpoints-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-endpoints-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-endpoints-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-endpoints-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-endpoints-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-endpoints-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-endpoints-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-endpoints-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-endpoints-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#endpointslice-v1-discovery-k8s-io" class="nav-item"><span class="gvk"><span class="k">EndpointSlice</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></A>
<UL id="endpointslice-v1-discovery-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-endpointslice-v1-discovery-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-endpointslice-v1-discovery-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-endpointslice-v1-discovery-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-endpointslice-v1-discovery-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-endpointslice-v1-discovery-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-endpointslice-v1-discovery-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-endpointslice-v1-discovery-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-endpointslice-v1-discovery-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-endpointslice-v1-discovery-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-endpointslice-v1-discovery-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-endpointslice-v1-discovery-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-endpointslice-v1-discovery-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-endpointslice-v1-discovery-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-endpointslice-v1-discovery-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-endpointslice-v1-discovery-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#ingress-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">Ingress</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
<UL id="ingress-v1-networking-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-ingress-v1-networking-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-ingress-v1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-ingress-v1-networking-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-ingress-v1-networking-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-ingress-v1-networking-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-ingress-v1-networking-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-ingress-v1-networking-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-ingress-v1-networking-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-ingress-v1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-ingress-v1-networking-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-ingress-v1-networking-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-ingress-v1-networking-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-ingress-v1-networking-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-ingress-v1-networking-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-ingress-v1-networking-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-ingress-v1-networking-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-ingress-v1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-ingress-v1-networking-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-ingress-v1-networking-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-ingress-v1-networking-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#ingressclass-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IngressClass</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
<UL id="ingressclass-v1-networking-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-ingressclass-v1-networking-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-ingressclass-v1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-ingressclass-v1-networking-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-ingressclass-v1-networking-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-ingressclass-v1-networking-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-ingressclass-v1-networking-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-ingressclass-v1-networking-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-ingressclass-v1-networking-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-ingressclass-v1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-ingressclass-v1-networking-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-ingressclass-v1-networking-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-ingressclass-v1-networking-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-ingressclass-v1-networking-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#service-v1-core" class="nav-item"><span class="gvk"><span class="k">Service</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="service-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-service-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-service-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-service-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-service-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-service-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-service-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-service-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-service-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-service-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-service-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-service-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-service-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-service-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-service-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-service-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-service-v1-core" class="nav-item">Status Operations</A>
<UL id="status-operations-service-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-service-v1-core" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-service-v1-core" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-service-v1-core" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#proxy-operations-service-v1-core" class="nav-item">Proxy Operations</A>
<UL id="proxy-operations-service-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-connect-proxy-service-v1-core" class="nav-item">Create Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#create-connect-proxy-path-service-v1-core" class="nav-item">Create Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-connect-proxy-service-v1-core" class="nav-item">Delete Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-connect-proxy-path-service-v1-core" class="nav-item">Delete Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#get-connect-proxy-service-v1-core" class="nav-item">Get Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#get-connect-proxy-path-service-v1-core" class="nav-item">Get Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#head-connect-proxy-service-v1-core" class="nav-item">Head Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#head-connect-proxy-path-service-v1-core" class="nav-item">Head Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-connect-proxy-service-v1-core" class="nav-item">Replace Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-connect-proxy-path-service-v1-core" class="nav-item">Replace Connect Proxy Path</A>
</LI>
</UL>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-1 has-children" data-level="1">
<A href="#config-and-storage-apis" class="nav-item">Config and Storage APIs</A>
<UL id="config-and-storage-apis-nav">
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#configmap-v1-core" class="nav-item"><span class="gvk"><span class="k">ConfigMap</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="configmap-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-configmap-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-configmap-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-configmap-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-configmap-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-configmap-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-configmap-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-configmap-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-configmap-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-configmap-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-configmap-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-configmap-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-configmap-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-configmap-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-configmap-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-configmap-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#csidriver-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">CSIDriver</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
<UL id="csidriver-v1-storage-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-csidriver-v1-storage-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-csidriver-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-csidriver-v1-storage-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-csidriver-v1-storage-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-csidriver-v1-storage-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-csidriver-v1-storage-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-csidriver-v1-storage-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-csidriver-v1-storage-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-csidriver-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-csidriver-v1-storage-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-csidriver-v1-storage-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-csidriver-v1-storage-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-csidriver-v1-storage-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#csinode-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">CSINode</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
<UL id="csinode-v1-storage-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-csinode-v1-storage-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-csinode-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-csinode-v1-storage-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-csinode-v1-storage-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-csinode-v1-storage-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-csinode-v1-storage-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-csinode-v1-storage-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-csinode-v1-storage-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-csinode-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-csinode-v1-storage-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-csinode-v1-storage-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-csinode-v1-storage-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-csinode-v1-storage-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#csistoragecapacity-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">CSIStorageCapacity</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
<UL id="csistoragecapacity-v1-storage-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-csistoragecapacity-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-csistoragecapacity-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-csistoragecapacity-v1-storage-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-csistoragecapacity-v1-storage-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-csistoragecapacity-v1-storage-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#secret-v1-core" class="nav-item"><span class="gvk"><span class="k">Secret</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="secret-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-secret-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-secret-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-secret-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-secret-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-secret-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-secret-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-secret-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-secret-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-secret-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-secret-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-secret-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-secret-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-secret-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-secret-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-secret-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#persistentvolumeclaim-v1-core" class="nav-item"><span class="gvk"><span class="k">PersistentVolumeClaim</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="persistentvolumeclaim-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-persistentvolumeclaim-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-persistentvolumeclaim-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-persistentvolumeclaim-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-persistentvolumeclaim-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-persistentvolumeclaim-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-persistentvolumeclaim-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-persistentvolumeclaim-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-persistentvolumeclaim-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-persistentvolumeclaim-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-persistentvolumeclaim-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-persistentvolumeclaim-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-persistentvolumeclaim-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-persistentvolumeclaim-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-persistentvolumeclaim-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-persistentvolumeclaim-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-persistentvolumeclaim-v1-core" class="nav-item">Status Operations</A>
<UL id="status-operations-persistentvolumeclaim-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-persistentvolumeclaim-v1-core" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-persistentvolumeclaim-v1-core" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-persistentvolumeclaim-v1-core" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#storageclass-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">StorageClass</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
<UL id="storageclass-v1-storage-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-storageclass-v1-storage-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-storageclass-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-storageclass-v1-storage-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-storageclass-v1-storage-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-storageclass-v1-storage-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-storageclass-v1-storage-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-storageclass-v1-storage-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-storageclass-v1-storage-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-storageclass-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-storageclass-v1-storage-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-storageclass-v1-storage-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-storageclass-v1-storage-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-storageclass-v1-storage-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item"><span class="gvk"><span class="k">StorageVersionMigration</span> <span class="v">v1alpha1</span> <span class="g">storagemigration.k8s.io</span></span></A>
<UL id="storageversionmigration-v1alpha1-storagemigration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#volume-v1-core" class="nav-item"><span class="gvk"><span class="k">Volume</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#volumeattachment-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">VolumeAttachment</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
<UL id="volumeattachment-v1-storage-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-volumeattachment-v1-storage-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-volumeattachment-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-volumeattachment-v1-storage-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-volumeattachment-v1-storage-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-volumeattachment-v1-storage-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-volumeattachment-v1-storage-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-volumeattachment-v1-storage-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-volumeattachment-v1-storage-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-volumeattachment-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-volumeattachment-v1-storage-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-volumeattachment-v1-storage-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-volumeattachment-v1-storage-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-volumeattachment-v1-storage-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-volumeattachment-v1-storage-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-volumeattachment-v1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-volumeattachment-v1-storage-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-volumeattachment-v1-storage-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-volumeattachment-v1-storage-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">VolumeAttributesClass</span> <span class="v">v1beta1</span> <span class="g">storage.k8s.io</span></span></A>
<UL id="volumeattributesclass-v1beta1-storage-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-volumeattributesclass-v1beta1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-volumeattributesclass-v1beta1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-volumeattributesclass-v1beta1-storage-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-1 has-children" data-level="1">
<A href="#metadata-apis" class="nav-item">Metadata APIs</A>
<UL id="metadata-apis-nav">
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item"><span class="gvk"><span class="k">ClusterTrustBundle</span> <span class="v">v1alpha1</span> <span class="g">certificates.k8s.io</span></span></A>
<UL id="clustertrustbundle-v1alpha1-certificates-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-clustertrustbundle-v1alpha1-certificates-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-clustertrustbundle-v1alpha1-certificates-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#controllerrevision-v1-apps" class="nav-item"><span class="gvk"><span class="k">ControllerRevision</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
<UL id="controllerrevision-v1-apps-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-controllerrevision-v1-apps" class="nav-item">Write Operations</A>
<UL id="write-operations-controllerrevision-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-controllerrevision-v1-apps" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-controllerrevision-v1-apps" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-controllerrevision-v1-apps" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-controllerrevision-v1-apps" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-controllerrevision-v1-apps" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-controllerrevision-v1-apps" class="nav-item">Read Operations</A>
<UL id="read-operations-controllerrevision-v1-apps-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-controllerrevision-v1-apps" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-controllerrevision-v1-apps" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-controllerrevision-v1-apps" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-controllerrevision-v1-apps" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-controllerrevision-v1-apps" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-controllerrevision-v1-apps" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceDefinition</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
<UL id="customresourcedefinition-v1-apiextensions-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-customresourcedefinition-v1-apiextensions-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-customresourcedefinition-v1-apiextensions-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-customresourcedefinition-v1-apiextensions-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-customresourcedefinition-v1-apiextensions-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#deviceclass-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceClass</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
<UL id="deviceclass-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-deviceclass-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-deviceclass-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-deviceclass-v1beta1-resource-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-deviceclass-v1beta1-resource-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#event-v1-events-k8s-io" class="nav-item"><span class="gvk"><span class="k">Event</span> <span class="v">v1</span> <span class="g">events.k8s.io</span></span></A>
<UL id="event-v1-events-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-event-v1-events-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-event-v1-events-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-event-v1-events-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-event-v1-events-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-event-v1-events-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-event-v1-events-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-event-v1-events-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-event-v1-events-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-event-v1-events-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-event-v1-events-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-event-v1-events-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-event-v1-events-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-event-v1-events-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-event-v1-events-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-event-v1-events-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#limitrange-v1-core" class="nav-item"><span class="gvk"><span class="k">LimitRange</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="limitrange-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-limitrange-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-limitrange-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-limitrange-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-limitrange-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-limitrange-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-limitrange-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-limitrange-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-limitrange-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-limitrange-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-limitrange-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-limitrange-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-limitrange-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-limitrange-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-limitrange-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-limitrange-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#horizontalpodautoscaler-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">HorizontalPodAutoscaler</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
<UL id="horizontalpodautoscaler-v2-autoscaling-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Write Operations</A>
<UL id="write-operations-horizontalpodautoscaler-v2-autoscaling-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Read Operations</A>
<UL id="read-operations-horizontalpodautoscaler-v2-autoscaling-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-horizontalpodautoscaler-v2-autoscaling" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-horizontalpodautoscaler-v2-autoscaling" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Status Operations</A>
<UL id="status-operations-horizontalpodautoscaler-v2-autoscaling-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-horizontalpodautoscaler-v2-autoscaling" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MutatingWebhookConfiguration</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
<UL id="mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#podtemplate-v1-core" class="nav-item"><span class="gvk"><span class="k">PodTemplate</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="podtemplate-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-podtemplate-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-podtemplate-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-podtemplate-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-podtemplate-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-podtemplate-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-podtemplate-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-podtemplate-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-podtemplate-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-podtemplate-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-podtemplate-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-podtemplate-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-podtemplate-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-podtemplate-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-podtemplate-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-podtemplate-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#poddisruptionbudget-v1-policy" class="nav-item"><span class="gvk"><span class="k">PodDisruptionBudget</span> <span class="v">v1</span> <span class="g">policy</span></span></A>
<UL id="poddisruptionbudget-v1-policy-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-poddisruptionbudget-v1-policy" class="nav-item">Write Operations</A>
<UL id="write-operations-poddisruptionbudget-v1-policy-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-poddisruptionbudget-v1-policy" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-poddisruptionbudget-v1-policy" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-poddisruptionbudget-v1-policy" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-poddisruptionbudget-v1-policy" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-poddisruptionbudget-v1-policy" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-poddisruptionbudget-v1-policy" class="nav-item">Read Operations</A>
<UL id="read-operations-poddisruptionbudget-v1-policy-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-poddisruptionbudget-v1-policy" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-poddisruptionbudget-v1-policy" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-poddisruptionbudget-v1-policy" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-poddisruptionbudget-v1-policy" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-poddisruptionbudget-v1-policy" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-poddisruptionbudget-v1-policy" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-poddisruptionbudget-v1-policy" class="nav-item">Status Operations</A>
<UL id="status-operations-poddisruptionbudget-v1-policy-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-poddisruptionbudget-v1-policy" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-poddisruptionbudget-v1-policy" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-poddisruptionbudget-v1-policy" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#priorityclass-v1-scheduling-k8s-io" class="nav-item"><span class="gvk"><span class="k">PriorityClass</span> <span class="v">v1</span> <span class="g">scheduling.k8s.io</span></span></A>
<UL id="priorityclass-v1-scheduling-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-priorityclass-v1-scheduling-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-priorityclass-v1-scheduling-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-priorityclass-v1-scheduling-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-priorityclass-v1-scheduling-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-priorityclass-v1-scheduling-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-priorityclass-v1-scheduling-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-priorityclass-v1-scheduling-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-priorityclass-v1-scheduling-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-priorityclass-v1-scheduling-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-priorityclass-v1-scheduling-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-priorityclass-v1-scheduling-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-priorityclass-v1-scheduling-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-priorityclass-v1-scheduling-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#resourceclaim-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceClaim</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
<UL id="resourceclaim-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-resourceclaim-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-resourceclaim-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-resourceclaim-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceClaimTemplate</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
<UL id="resourceclaimtemplate-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-resourceclaimtemplate-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-resourceclaimtemplate-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-resourceclaimtemplate-v1beta1-resource-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#resourceslice-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceSlice</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
<UL id="resourceslice-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-resourceslice-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-resourceslice-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-resourceslice-v1beta1-resource-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-resourceslice-v1beta1-resource-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ValidatingAdmissionPolicy</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
<UL id="validatingadmissionpolicy-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-validatingadmissionpolicy-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-validatingadmissionpolicy-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-validatingadmissionpolicy-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-validatingadmissionpolicy-v1-admissionregistration-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ValidatingAdmissionPolicyBinding</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
<UL id="validatingadmissionpolicybinding-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ValidatingWebhookConfiguration</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
<UL id="validatingwebhookconfiguration-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-1 has-children" data-level="1">
<A href="#cluster-apis" class="nav-item">Cluster APIs</A>
<UL id="cluster-apis-nav">
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#apiservice-v1-apiregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">APIService</span> <span class="v">v1</span> <span class="g">apiregistration.k8s.io</span></span></A>
<UL id="apiservice-v1-apiregistration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-apiservice-v1-apiregistration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-apiservice-v1-apiregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-apiservice-v1-apiregistration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-apiservice-v1-apiregistration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-apiservice-v1-apiregistration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-apiservice-v1-apiregistration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-apiservice-v1-apiregistration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-apiservice-v1-apiregistration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-apiservice-v1-apiregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-apiservice-v1-apiregistration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-apiservice-v1-apiregistration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-apiservice-v1-apiregistration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-apiservice-v1-apiregistration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-apiservice-v1-apiregistration-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-apiservice-v1-apiregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-apiservice-v1-apiregistration-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-apiservice-v1-apiregistration-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-apiservice-v1-apiregistration-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#binding-v1-core" class="nav-item"><span class="gvk"><span class="k">Binding</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="binding-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-binding-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-binding-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-binding-v1-core" class="nav-item">Create</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#certificatesigningrequest-v1-certificates-k8s-io" class="nav-item"><span class="gvk"><span class="k">CertificateSigningRequest</span> <span class="v">v1</span> <span class="g">certificates.k8s.io</span></span></A>
<UL id="certificatesigningrequest-v1-certificates-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-certificatesigningrequest-v1-certificates-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-certificatesigningrequest-v1-certificates-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-certificatesigningrequest-v1-certificates-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-certificatesigningrequest-v1-certificates-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#clusterrole-v1-rbac-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">ClusterRole</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></A>
<UL id="clusterrole-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-clusterrole-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-clusterrole-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">ClusterRoleBinding</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></A>
<UL id="clusterrolebinding-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#componentstatus-v1-core" class="nav-item"><span class="gvk"><span class="k">ComponentStatus</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="componentstatus-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-componentstatus-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-componentstatus-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-componentstatus-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-componentstatus-v1-core" class="nav-item">List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">FlowSchema</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
<UL id="flowschema-v1-flowcontrol-apiserver-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-flowschema-v1-flowcontrol-apiserver-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-flowschema-v1-flowcontrol-apiserver-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-flowschema-v1-flowcontrol-apiserver-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-flowschema-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#ipaddress-v1beta1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IPAddress</span> <span class="v">v1beta1</span> <span class="g">networking.k8s.io</span></span></A>
<UL id="ipaddress-v1beta1-networking-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-ipaddress-v1beta1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-ipaddress-v1beta1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-ipaddress-v1beta1-networking-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-ipaddress-v1beta1-networking-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#lease-v1-coordination-k8s-io" class="nav-item"><span class="gvk"><span class="k">Lease</span> <span class="v">v1</span> <span class="g">coordination.k8s.io</span></span></A>
<UL id="lease-v1-coordination-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-lease-v1-coordination-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-lease-v1-coordination-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-lease-v1-coordination-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-lease-v1-coordination-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-lease-v1-coordination-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-lease-v1-coordination-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-lease-v1-coordination-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-lease-v1-coordination-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-lease-v1-coordination-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-lease-v1-coordination-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-lease-v1-coordination-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-lease-v1-coordination-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-lease-v1-coordination-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-lease-v1-coordination-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-lease-v1-coordination-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item"><span class="gvk"><span class="k">LeaseCandidate</span> <span class="v">v1alpha2</span> <span class="g">coordination.k8s.io</span></span></A>
<UL id="leasecandidate-v1alpha2-coordination-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-leasecandidate-v1alpha2-coordination-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-leasecandidate-v1alpha2-coordination-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-leasecandidate-v1alpha2-coordination-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#localsubjectaccessreview-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">LocalSubjectAccessReview</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
<UL id="localsubjectaccessreview-v1-authorization-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-localsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-localsubjectaccessreview-v1-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-localsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">Create</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#namespace-v1-core" class="nav-item"><span class="gvk"><span class="k">Namespace</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="namespace-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-namespace-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-namespace-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-namespace-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-namespace-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-namespace-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-namespace-v1-core" class="nav-item">Delete</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-namespace-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-namespace-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-namespace-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-namespace-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-namespace-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-namespace-v1-core" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-namespace-v1-core" class="nav-item">Status Operations</A>
<UL id="status-operations-namespace-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-namespace-v1-core" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-namespace-v1-core" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-namespace-v1-core" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#node-v1-core" class="nav-item"><span class="gvk"><span class="k">Node</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="node-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-node-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-node-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-node-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-node-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-node-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-node-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-node-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-node-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-node-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-node-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-node-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-node-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-node-v1-core" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-node-v1-core" class="nav-item">Status Operations</A>
<UL id="status-operations-node-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-node-v1-core" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-node-v1-core" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-node-v1-core" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#proxy-operations-node-v1-core" class="nav-item">Proxy Operations</A>
<UL id="proxy-operations-node-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-connect-proxy-node-v1-core" class="nav-item">Create Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#create-connect-proxy-path-node-v1-core" class="nav-item">Create Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-connect-proxy-node-v1-core" class="nav-item">Delete Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-connect-proxy-path-node-v1-core" class="nav-item">Delete Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#get-connect-proxy-node-v1-core" class="nav-item">Get Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#get-connect-proxy-path-node-v1-core" class="nav-item">Get Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#head-connect-proxy-node-v1-core" class="nav-item">Head Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#head-connect-proxy-path-node-v1-core" class="nav-item">Head Connect Proxy Path</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-connect-proxy-node-v1-core" class="nav-item">Replace Connect Proxy</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-connect-proxy-path-node-v1-core" class="nav-item">Replace Connect Proxy Path</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#persistentvolume-v1-core" class="nav-item"><span class="gvk"><span class="k">PersistentVolume</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="persistentvolume-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-persistentvolume-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-persistentvolume-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-persistentvolume-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-persistentvolume-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-persistentvolume-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-persistentvolume-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-persistentvolume-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-persistentvolume-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-persistentvolume-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-persistentvolume-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-persistentvolume-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-persistentvolume-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-persistentvolume-v1-core" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-persistentvolume-v1-core" class="nav-item">Status Operations</A>
<UL id="status-operations-persistentvolume-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-persistentvolume-v1-core" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-persistentvolume-v1-core" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-persistentvolume-v1-core" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">PriorityLevelConfiguration</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
<UL id="prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#resourcequota-v1-core" class="nav-item"><span class="gvk"><span class="k">ResourceQuota</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="resourcequota-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-resourcequota-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-resourcequota-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-resourcequota-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-resourcequota-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-resourcequota-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-resourcequota-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-resourcequota-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-resourcequota-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-resourcequota-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-resourcequota-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-resourcequota-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-resourcequota-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-resourcequota-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-resourcequota-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-resourcequota-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-resourcequota-v1-core" class="nav-item">Status Operations</A>
<UL id="status-operations-resourcequota-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-resourcequota-v1-core" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-resourcequota-v1-core" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-resourcequota-v1-core" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#role-v1-rbac-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">Role</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></A>
<UL id="role-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-role-v1-rbac-authorization-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-role-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-role-v1-rbac-authorization-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-role-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-role-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-role-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-role-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-role-v1-rbac-authorization-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-role-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-role-v1-rbac-authorization-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-role-v1-rbac-authorization-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-role-v1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-role-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-role-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-role-v1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#rolebinding-v1-rbac-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">RoleBinding</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></A>
<UL id="rolebinding-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-rolebinding-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-rolebinding-v1-rbac-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#runtimeclass-v1-node-k8s-io" class="nav-item"><span class="gvk"><span class="k">RuntimeClass</span> <span class="v">v1</span> <span class="g">node.k8s.io</span></span></A>
<UL id="runtimeclass-v1-node-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-runtimeclass-v1-node-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-runtimeclass-v1-node-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-runtimeclass-v1-node-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-runtimeclass-v1-node-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-runtimeclass-v1-node-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-runtimeclass-v1-node-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-runtimeclass-v1-node-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-runtimeclass-v1-node-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-runtimeclass-v1-node-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-runtimeclass-v1-node-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-runtimeclass-v1-node-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-runtimeclass-v1-node-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-runtimeclass-v1-node-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#selfsubjectaccessreview-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">SelfSubjectAccessReview</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
<UL id="selfsubjectaccessreview-v1-authorization-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-selfsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-selfsubjectaccessreview-v1-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-selfsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">Create</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#selfsubjectreview-v1-authentication-k8s-io" class="nav-item"><span class="gvk"><span class="k">SelfSubjectReview</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></A>
<UL id="selfsubjectreview-v1-authentication-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-selfsubjectreview-v1-authentication-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-selfsubjectreview-v1-authentication-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-selfsubjectreview-v1-authentication-k8s-io" class="nav-item">Create</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#selfsubjectrulesreview-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">SelfSubjectRulesReview</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
<UL id="selfsubjectrulesreview-v1-authorization-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-selfsubjectrulesreview-v1-authorization-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-selfsubjectrulesreview-v1-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-selfsubjectrulesreview-v1-authorization-k8s-io" class="nav-item">Create</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#serviceaccount-v1-core" class="nav-item"><span class="gvk"><span class="k">ServiceAccount</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="serviceaccount-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-serviceaccount-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-serviceaccount-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-serviceaccount-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-serviceaccount-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-serviceaccount-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-serviceaccount-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-serviceaccount-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-serviceaccount-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-serviceaccount-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-serviceaccount-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-serviceaccount-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-serviceaccount-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-serviceaccount-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-serviceaccount-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-serviceaccount-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#servicecidr-v1beta1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">ServiceCIDR</span> <span class="v">v1beta1</span> <span class="g">networking.k8s.io</span></span></A>
<UL id="servicecidr-v1beta1-networking-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-servicecidr-v1beta1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-servicecidr-v1beta1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-servicecidr-v1beta1-networking-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-servicecidr-v1beta1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-servicecidr-v1beta1-networking-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">StorageVersion</span> <span class="v">v1alpha1</span> <span class="g">internal.apiserver.k8s.io</span></span></A>
<UL id="storageversion-v1alpha1-internal-apiserver-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-storageversion-v1alpha1-internal-apiserver-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-storageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item"><span class="gvk"><span class="k">StorageVersionMigration</span> <span class="v">v1alpha1</span> <span class="g">storagemigration.k8s.io</span></span></A>
<UL id="storageversionmigration-v1alpha1-storagemigration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-storageversionmigration-v1alpha1-storagemigration-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#subjectaccessreview-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">SubjectAccessReview</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
<UL id="subjectaccessreview-v1-authorization-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-subjectaccessreview-v1-authorization-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-subjectaccessreview-v1-authorization-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-subjectaccessreview-v1-authorization-k8s-io" class="nav-item">Create</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#tokenrequest-v1-authentication-k8s-io" class="nav-item"><span class="gvk"><span class="k">TokenRequest</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#tokenreview-v1-authentication-k8s-io" class="nav-item"><span class="gvk"><span class="k">TokenReview</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></A>
<UL id="tokenreview-v1-authentication-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-tokenreview-v1-authentication-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-tokenreview-v1-authentication-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-tokenreview-v1-authentication-k8s-io" class="nav-item">Create</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#networkpolicy-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">NetworkPolicy</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
<UL id="networkpolicy-v1-networking-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-networkpolicy-v1-networking-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-networkpolicy-v1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-networkpolicy-v1-networking-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-networkpolicy-v1-networking-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-networkpolicy-v1-networking-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-networkpolicy-v1-networking-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-networkpolicy-v1-networking-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-networkpolicy-v1-networking-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-networkpolicy-v1-networking-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-networkpolicy-v1-networking-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-networkpolicy-v1-networking-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-networkpolicy-v1-networking-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-networkpolicy-v1-networking-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-networkpolicy-v1-networking-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-networkpolicy-v1-networking-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MutatingAdmissionPolicy</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
<UL id="mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MutatingAdmissionPolicyBinding</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
<UL id="mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-1 has-children" data-level="1">
<A href="#definitions" class="nav-item">DEFINITIONS</A>
<UL id="definitions-nav">
<LI class="nav-level level-2" data-level="2">
<A href="#apigroup-v1-meta" class="nav-item"><span class="gvk"><span class="k">APIGroup</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#apiresource-v1-meta" class="nav-item"><span class="gvk"><span class="k">APIResource</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#apiservicecondition-v1-apiregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">APIServiceCondition</span> <span class="v">v1</span> <span class="g">apiregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#apiversions-v1-meta" class="nav-item"><span class="gvk"><span class="k">APIVersions</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#awselasticblockstorevolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">AWSElasticBlockStoreVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#affinity-v1-core" class="nav-item"><span class="gvk"><span class="k">Affinity</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#aggregationrule-v1-rbac-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">AggregationRule</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#allocateddevicestatus-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">AllocatedDeviceStatus</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#allocationresult-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">AllocationResult</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#apparmorprofile-v1-core" class="nav-item"><span class="gvk"><span class="k">AppArmorProfile</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#applyconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ApplyConfiguration</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#attachedvolume-v1-core" class="nav-item"><span class="gvk"><span class="k">AttachedVolume</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#auditannotation-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">AuditAnnotation</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#azurediskvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">AzureDiskVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#azurefilepersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">AzureFilePersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#azurefilevolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">AzureFileVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#basicdevice-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">BasicDevice</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#boundobjectreference-v1-authentication-k8s-io" class="nav-item"><span class="gvk"><span class="k">BoundObjectReference</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#celdeviceselector-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">CELDeviceSelector</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#csinodedriver-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">CSINodeDriver</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#csipersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">CSIPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#csivolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">CSIVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#capabilities-v1-core" class="nav-item"><span class="gvk"><span class="k">Capabilities</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#cephfspersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">CephFSPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#cephfsvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">CephFSVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#certificatesigningrequestcondition-v1-certificates-k8s-io" class="nav-item"><span class="gvk"><span class="k">CertificateSigningRequestCondition</span> <span class="v">v1</span> <span class="g">certificates.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#cinderpersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">CinderPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#cindervolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">CinderVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#clientipconfig-v1-core" class="nav-item"><span class="gvk"><span class="k">ClientIPConfig</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#clustertrustbundleprojection-v1-core" class="nav-item"><span class="gvk"><span class="k">ClusterTrustBundleProjection</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#componentcondition-v1-core" class="nav-item"><span class="gvk"><span class="k">ComponentCondition</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#condition-v1-meta" class="nav-item"><span class="gvk"><span class="k">Condition</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#configmapenvsource-v1-core" class="nav-item"><span class="gvk"><span class="k">ConfigMapEnvSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#configmapkeyselector-v1-core" class="nav-item"><span class="gvk"><span class="k">ConfigMapKeySelector</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#configmapnodeconfigsource-v1-core" class="nav-item"><span class="gvk"><span class="k">ConfigMapNodeConfigSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#configmapprojection-v1-core" class="nav-item"><span class="gvk"><span class="k">ConfigMapProjection</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#configmapvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">ConfigMapVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containerimage-v1-core" class="nav-item"><span class="gvk"><span class="k">ContainerImage</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containerport-v1-core" class="nav-item"><span class="gvk"><span class="k">ContainerPort</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containerresizepolicy-v1-core" class="nav-item"><span class="gvk"><span class="k">ContainerResizePolicy</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containerresourcemetricsource-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">ContainerResourceMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containerresourcemetricstatus-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">ContainerResourceMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containerstate-v1-core" class="nav-item"><span class="gvk"><span class="k">ContainerState</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containerstaterunning-v1-core" class="nav-item"><span class="gvk"><span class="k">ContainerStateRunning</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containerstateterminated-v1-core" class="nav-item"><span class="gvk"><span class="k">ContainerStateTerminated</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containerstatewaiting-v1-core" class="nav-item"><span class="gvk"><span class="k">ContainerStateWaiting</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#containeruser-v1-core" class="nav-item"><span class="gvk"><span class="k">ContainerUser</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#crossversionobjectreference-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">CrossVersionObjectReference</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#customresourcecolumndefinition-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceColumnDefinition</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#customresourceconversion-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceConversion</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#customresourcedefinitioncondition-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceDefinitionCondition</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#customresourcedefinitionnames-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceDefinitionNames</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#customresourcedefinitionversion-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceDefinitionVersion</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#customresourcesubresourcescale-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceSubresourceScale</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#customresourcesubresourcestatus-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceSubresourceStatus</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#customresourcesubresources-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceSubresources</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#customresourcevalidation-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">CustomResourceValidation</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#daemonendpoint-v1-core" class="nav-item"><span class="gvk"><span class="k">DaemonEndpoint</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#daemonsetcondition-v1-apps" class="nav-item"><span class="gvk"><span class="k">DaemonSetCondition</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#daemonsetupdatestrategy-v1-apps" class="nav-item"><span class="gvk"><span class="k">DaemonSetUpdateStrategy</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deleteoptions-v1-meta" class="nav-item"><span class="gvk"><span class="k">DeleteOptions</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deploymentcondition-v1-apps" class="nav-item"><span class="gvk"><span class="k">DeploymentCondition</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#device-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">Device</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceallocationconfiguration-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceAllocationConfiguration</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceallocationresult-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceAllocationResult</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceattribute-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceAttribute</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#devicecapacity-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceCapacity</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceclaim-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceClaim</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceclaimconfiguration-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceClaimConfiguration</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceclassconfiguration-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceClassConfiguration</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceconstraint-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceConstraint</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#devicerequest-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceRequest</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#devicerequestallocationresult-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceRequestAllocationResult</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceselector-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceSelector</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#downwardapiprojection-v1-core" class="nav-item"><span class="gvk"><span class="k">DownwardAPIProjection</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#downwardapivolumefile-v1-core" class="nav-item"><span class="gvk"><span class="k">DownwardAPIVolumeFile</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#downwardapivolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">DownwardAPIVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#emptydirvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">EmptyDirVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#endpoint-v1-discovery-k8s-io" class="nav-item"><span class="gvk"><span class="k">Endpoint</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#endpointaddress-v1-core" class="nav-item"><span class="gvk"><span class="k">EndpointAddress</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#endpointconditions-v1-discovery-k8s-io" class="nav-item"><span class="gvk"><span class="k">EndpointConditions</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#endpointhints-v1-discovery-k8s-io" class="nav-item"><span class="gvk"><span class="k">EndpointHints</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#endpointport-v1-core" class="nav-item"><span class="gvk"><span class="k">EndpointPort</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#endpointsubset-v1-core" class="nav-item"><span class="gvk"><span class="k">EndpointSubset</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#envfromsource-v1-core" class="nav-item"><span class="gvk"><span class="k">EnvFromSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#envvar-v1-core" class="nav-item"><span class="gvk"><span class="k">EnvVar</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#envvarsource-v1-core" class="nav-item"><span class="gvk"><span class="k">EnvVarSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ephemeralcontainer-v1-core" class="nav-item"><span class="gvk"><span class="k">EphemeralContainer</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ephemeralvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">EphemeralVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#eventseries-v1-events-k8s-io" class="nav-item"><span class="gvk"><span class="k">EventSeries</span> <span class="v">v1</span> <span class="g">events.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#eventsource-v1-core" class="nav-item"><span class="gvk"><span class="k">EventSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#eviction-v1-policy" class="nav-item"><span class="gvk"><span class="k">Eviction</span> <span class="v">v1</span> <span class="g">policy</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#execaction-v1-core" class="nav-item"><span class="gvk"><span class="k">ExecAction</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#exemptprioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">ExemptPriorityLevelConfiguration</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#expressionwarning-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ExpressionWarning</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#externaldocumentation-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">ExternalDocumentation</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#externalmetricsource-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">ExternalMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#externalmetricstatus-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">ExternalMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#fcvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">FCVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#fieldselectorattributes-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">FieldSelectorAttributes</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#fieldselectorrequirement-v1-meta" class="nav-item"><span class="gvk"><span class="k">FieldSelectorRequirement</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#fieldsv1-v1-meta" class="nav-item"><span class="gvk"><span class="k">FieldsV1</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#flexpersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">FlexPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#flexvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">FlexVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#flockervolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">FlockerVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#flowdistinguishermethod-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">FlowDistinguisherMethod</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#flowschemacondition-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">FlowSchemaCondition</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#forzone-v1-discovery-k8s-io" class="nav-item"><span class="gvk"><span class="k">ForZone</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#gcepersistentdiskvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">GCEPersistentDiskVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#grpcaction-v1-core" class="nav-item"><span class="gvk"><span class="k">GRPCAction</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#gitrepovolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">GitRepoVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#glusterfspersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">GlusterfsPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#glusterfsvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">GlusterfsVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#groupsubject-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">GroupSubject</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#groupversionfordiscovery-v1-meta" class="nav-item"><span class="gvk"><span class="k">GroupVersionForDiscovery</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#groupversionresource-v1alpha1-storagemigration-k8s-io" class="nav-item"><span class="gvk"><span class="k">GroupVersionResource</span> <span class="v">v1alpha1</span> <span class="g">storagemigration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#hpascalingpolicy-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">HPAScalingPolicy</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#hpascalingrules-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">HPAScalingRules</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#httpgetaction-v1-core" class="nav-item"><span class="gvk"><span class="k">HTTPGetAction</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#httpheader-v1-core" class="nav-item"><span class="gvk"><span class="k">HTTPHeader</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#httpingresspath-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">HTTPIngressPath</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#httpingressrulevalue-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">HTTPIngressRuleValue</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#horizontalpodautoscalerbehavior-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">HorizontalPodAutoscalerBehavior</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#horizontalpodautoscalercondition-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">HorizontalPodAutoscalerCondition</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#hostalias-v1-core" class="nav-item"><span class="gvk"><span class="k">HostAlias</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#hostip-v1-core" class="nav-item"><span class="gvk"><span class="k">HostIP</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#hostpathvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">HostPathVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ipblock-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IPBlock</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#iscsipersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">ISCSIPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#iscsivolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">ISCSIVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#imagevolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">ImageVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ingressbackend-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IngressBackend</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ingressclassparametersreference-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IngressClassParametersReference</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ingressloadbalanceringress-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IngressLoadBalancerIngress</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ingressloadbalancerstatus-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IngressLoadBalancerStatus</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ingressportstatus-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IngressPortStatus</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ingressrule-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IngressRule</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ingressservicebackend-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IngressServiceBackend</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ingresstls-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">IngressTLS</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#json-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">JSON</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#jsonpatch-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">JSONPatch</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#jsonschemaprops-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">JSONSchemaProps</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#jsonschemapropsorarray-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">JSONSchemaPropsOrArray</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#jsonschemapropsorbool-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">JSONSchemaPropsOrBool</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#jobcondition-v1-batch" class="nav-item"><span class="gvk"><span class="k">JobCondition</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#jobtemplatespec-v1-batch" class="nav-item"><span class="gvk"><span class="k">JobTemplateSpec</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#keytopath-v1-core" class="nav-item"><span class="gvk"><span class="k">KeyToPath</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#labelselector-v1-meta" class="nav-item"><span class="gvk"><span class="k">LabelSelector</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#labelselectorattributes-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">LabelSelectorAttributes</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#labelselectorrequirement-v1-meta" class="nav-item"><span class="gvk"><span class="k">LabelSelectorRequirement</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#lifecycle-v1-core" class="nav-item"><span class="gvk"><span class="k">Lifecycle</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#lifecyclehandler-v1-core" class="nav-item"><span class="gvk"><span class="k">LifecycleHandler</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#limitrangeitem-v1-core" class="nav-item"><span class="gvk"><span class="k">LimitRangeItem</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#limitresponse-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">LimitResponse</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#limitedprioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">LimitedPriorityLevelConfiguration</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#linuxcontaineruser-v1-core" class="nav-item"><span class="gvk"><span class="k">LinuxContainerUser</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#listmeta-v1-meta" class="nav-item"><span class="gvk"><span class="k">ListMeta</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#loadbalanceringress-v1-core" class="nav-item"><span class="gvk"><span class="k">LoadBalancerIngress</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#loadbalancerstatus-v1-core" class="nav-item"><span class="gvk"><span class="k">LoadBalancerStatus</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#localobjectreference-v1-core" class="nav-item"><span class="gvk"><span class="k">LocalObjectReference</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#localvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">LocalVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#managedfieldsentry-v1-meta" class="nav-item"><span class="gvk"><span class="k">ManagedFieldsEntry</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#matchcondition-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MatchCondition</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#matchresources-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MatchResources</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#metricidentifier-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">MetricIdentifier</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#metricspec-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">MetricSpec</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#metricstatus-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">MetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#metrictarget-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">MetricTarget</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#metricvaluestatus-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">MetricValueStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#microtime-v1-meta" class="nav-item"><span class="gvk"><span class="k">MicroTime</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#migrationcondition-v1alpha1-storagemigration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MigrationCondition</span> <span class="v">v1alpha1</span> <span class="g">storagemigration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#modifyvolumestatus-v1-core" class="nav-item"><span class="gvk"><span class="k">ModifyVolumeStatus</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#mutatingwebhook-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MutatingWebhook</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#mutation-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">Mutation</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nfsvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">NFSVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#namedrulewithoperations-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">NamedRuleWithOperations</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#namespacecondition-v1-core" class="nav-item"><span class="gvk"><span class="k">NamespaceCondition</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#networkdevicedata-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">NetworkDeviceData</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#networkpolicyegressrule-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">NetworkPolicyEgressRule</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#networkpolicyingressrule-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">NetworkPolicyIngressRule</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#networkpolicypeer-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">NetworkPolicyPeer</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#networkpolicyport-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">NetworkPolicyPort</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodeaddress-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeAddress</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodeaffinity-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeAffinity</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodecondition-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeCondition</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodeconfigsource-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeConfigSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodeconfigstatus-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeConfigStatus</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodedaemonendpoints-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeDaemonEndpoints</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodefeatures-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeFeatures</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#noderuntimehandler-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeRuntimeHandler</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#noderuntimehandlerfeatures-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeRuntimeHandlerFeatures</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodeselector-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeSelector</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodeselectorrequirement-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeSelectorRequirement</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodeselectorterm-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeSelectorTerm</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nodesysteminfo-v1-core" class="nav-item"><span class="gvk"><span class="k">NodeSystemInfo</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nonresourceattributes-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">NonResourceAttributes</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nonresourcepolicyrule-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">NonResourcePolicyRule</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#nonresourcerule-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">NonResourceRule</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#objectfieldselector-v1-core" class="nav-item"><span class="gvk"><span class="k">ObjectFieldSelector</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#objectmeta-v1-meta" class="nav-item"><span class="gvk"><span class="k">ObjectMeta</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#objectmetricsource-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">ObjectMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#objectmetricstatus-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">ObjectMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#objectreference-v1-core" class="nav-item"><span class="gvk"><span class="k">ObjectReference</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#opaquedeviceconfiguration-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">OpaqueDeviceConfiguration</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#overhead-v1-node-k8s-io" class="nav-item"><span class="gvk"><span class="k">Overhead</span> <span class="v">v1</span> <span class="g">node.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#ownerreference-v1-meta" class="nav-item"><span class="gvk"><span class="k">OwnerReference</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#paramkind-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ParamKind</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#paramref-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ParamRef</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#parentreference-v1beta1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">ParentReference</span> <span class="v">v1beta1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#patch-v1-meta" class="nav-item"><span class="gvk"><span class="k">Patch</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#persistentvolumeclaimcondition-v1-core" class="nav-item"><span class="gvk"><span class="k">PersistentVolumeClaimCondition</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#persistentvolumeclaimtemplate-v1-core" class="nav-item"><span class="gvk"><span class="k">PersistentVolumeClaimTemplate</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#persistentvolumeclaimvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">PersistentVolumeClaimVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#photonpersistentdiskvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">PhotonPersistentDiskVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podaffinity-v1-core" class="nav-item"><span class="gvk"><span class="k">PodAffinity</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podaffinityterm-v1-core" class="nav-item"><span class="gvk"><span class="k">PodAffinityTerm</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podantiaffinity-v1-core" class="nav-item"><span class="gvk"><span class="k">PodAntiAffinity</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podcondition-v1-core" class="nav-item"><span class="gvk"><span class="k">PodCondition</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#poddnsconfig-v1-core" class="nav-item"><span class="gvk"><span class="k">PodDNSConfig</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#poddnsconfigoption-v1-core" class="nav-item"><span class="gvk"><span class="k">PodDNSConfigOption</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podfailurepolicy-v1-batch" class="nav-item"><span class="gvk"><span class="k">PodFailurePolicy</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podfailurepolicyonexitcodesrequirement-v1-batch" class="nav-item"><span class="gvk"><span class="k">PodFailurePolicyOnExitCodesRequirement</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podfailurepolicyonpodconditionspattern-v1-batch" class="nav-item"><span class="gvk"><span class="k">PodFailurePolicyOnPodConditionsPattern</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podfailurepolicyrule-v1-batch" class="nav-item"><span class="gvk"><span class="k">PodFailurePolicyRule</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podip-v1-core" class="nav-item"><span class="gvk"><span class="k">PodIP</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podos-v1-core" class="nav-item"><span class="gvk"><span class="k">PodOS</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podreadinessgate-v1-core" class="nav-item"><span class="gvk"><span class="k">PodReadinessGate</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podresourceclaim-v1-core" class="nav-item"><span class="gvk"><span class="k">PodResourceClaim</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podschedulinggate-v1-core" class="nav-item"><span class="gvk"><span class="k">PodSchedulingGate</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podsecuritycontext-v1-core" class="nav-item"><span class="gvk"><span class="k">PodSecurityContext</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podsmetricsource-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">PodsMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#podsmetricstatus-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">PodsMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#policyrule-v1-rbac-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">PolicyRule</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#policyruleswithsubjects-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">PolicyRulesWithSubjects</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#portstatus-v1-core" class="nav-item"><span class="gvk"><span class="k">PortStatus</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#portworxvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">PortworxVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#preconditions-v1-meta" class="nav-item"><span class="gvk"><span class="k">Preconditions</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#preferredschedulingterm-v1-core" class="nav-item"><span class="gvk"><span class="k">PreferredSchedulingTerm</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#prioritylevelconfigurationcondition-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">PriorityLevelConfigurationCondition</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#prioritylevelconfigurationreference-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">PriorityLevelConfigurationReference</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#probe-v1-core" class="nav-item"><span class="gvk"><span class="k">Probe</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#projectedvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">ProjectedVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#quantity-resource-core" class="nav-item"><span class="gvk"><span class="k">Quantity</span> <span class="v">resource</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#queuingconfiguration-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">QueuingConfiguration</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#quobytevolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">QuobyteVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#rbdpersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">RBDPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#rbdvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">RBDVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#replicasetcondition-v1-apps" class="nav-item"><span class="gvk"><span class="k">ReplicaSetCondition</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#replicationcontrollercondition-v1-core" class="nav-item"><span class="gvk"><span class="k">ReplicationControllerCondition</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourceattributes-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceAttributes</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourceclaim-v1-core" class="nav-item"><span class="gvk"><span class="k">ResourceClaim</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourceclaimconsumerreference-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceClaimConsumerReference</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcefieldselector-v1-core" class="nav-item"><span class="gvk"><span class="k">ResourceFieldSelector</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcehealth-v1-core" class="nav-item"><span class="gvk"><span class="k">ResourceHealth</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcemetricsource-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">ResourceMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcemetricstatus-v2-autoscaling" class="nav-item"><span class="gvk"><span class="k">ResourceMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcepolicyrule-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourcePolicyRule</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcepool-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourcePool</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcerequirements-v1-core" class="nav-item"><span class="gvk"><span class="k">ResourceRequirements</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcerule-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceRule</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcestatus-v1-core" class="nav-item"><span class="gvk"><span class="k">ResourceStatus</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#roleref-v1-rbac-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">RoleRef</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#rollingupdatestatefulsetstrategy-v1-apps" class="nav-item"><span class="gvk"><span class="k">RollingUpdateStatefulSetStrategy</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#rulewithoperations-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">RuleWithOperations</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#selinuxoptions-v1-core" class="nav-item"><span class="gvk"><span class="k">SELinuxOptions</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#scale-v1-autoscaling" class="nav-item"><span class="gvk"><span class="k">Scale</span> <span class="v">v1</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#scaleiopersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">ScaleIOPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#scaleiovolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">ScaleIOVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#scheduling-v1-node-k8s-io" class="nav-item"><span class="gvk"><span class="k">Scheduling</span> <span class="v">v1</span> <span class="g">node.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#scopeselector-v1-core" class="nav-item"><span class="gvk"><span class="k">ScopeSelector</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#scopedresourceselectorrequirement-v1-core" class="nav-item"><span class="gvk"><span class="k">ScopedResourceSelectorRequirement</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#seccompprofile-v1-core" class="nav-item"><span class="gvk"><span class="k">SeccompProfile</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#secretenvsource-v1-core" class="nav-item"><span class="gvk"><span class="k">SecretEnvSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#secretkeyselector-v1-core" class="nav-item"><span class="gvk"><span class="k">SecretKeySelector</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#secretprojection-v1-core" class="nav-item"><span class="gvk"><span class="k">SecretProjection</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#secretreference-v1-core" class="nav-item"><span class="gvk"><span class="k">SecretReference</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#secretvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">SecretVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#securitycontext-v1-core" class="nav-item"><span class="gvk"><span class="k">SecurityContext</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#selectablefield-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">SelectableField</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#serveraddressbyclientcidr-v1-meta" class="nav-item"><span class="gvk"><span class="k">ServerAddressByClientCIDR</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#serverstorageversion-v1alpha1-internal-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">ServerStorageVersion</span> <span class="v">v1alpha1</span> <span class="g">internal.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#serviceaccountsubject-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">ServiceAccountSubject</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#serviceaccounttokenprojection-v1-core" class="nav-item"><span class="gvk"><span class="k">ServiceAccountTokenProjection</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#servicebackendport-v1-networking-k8s-io" class="nav-item"><span class="gvk"><span class="k">ServiceBackendPort</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#serviceport-v1-core" class="nav-item"><span class="gvk"><span class="k">ServicePort</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#servicereference-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ServiceReference</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#sessionaffinityconfig-v1-core" class="nav-item"><span class="gvk"><span class="k">SessionAffinityConfig</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#sleepaction-v1-core" class="nav-item"><span class="gvk"><span class="k">SleepAction</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#statefulsetcondition-v1-apps" class="nav-item"><span class="gvk"><span class="k">StatefulSetCondition</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#statefulsetordinals-v1-apps" class="nav-item"><span class="gvk"><span class="k">StatefulSetOrdinals</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#statefulsetpersistentvolumeclaimretentionpolicy-v1-apps" class="nav-item"><span class="gvk"><span class="k">StatefulSetPersistentVolumeClaimRetentionPolicy</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#statefulsetupdatestrategy-v1-apps" class="nav-item"><span class="gvk"><span class="k">StatefulSetUpdateStrategy</span> <span class="v">v1</span> <span class="g">apps</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#status-v1-meta" class="nav-item"><span class="gvk"><span class="k">Status</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#statuscause-v1-meta" class="nav-item"><span class="gvk"><span class="k">StatusCause</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#statusdetails-v1-meta" class="nav-item"><span class="gvk"><span class="k">StatusDetails</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#storageospersistentvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">StorageOSPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#storageosvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">StorageOSVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#storageversioncondition-v1alpha1-internal-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">StorageVersionCondition</span> <span class="v">v1alpha1</span> <span class="g">internal.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#subject-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">Subject</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#subjectrulesreviewstatus-v1-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">SubjectRulesReviewStatus</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#successpolicy-v1-batch" class="nav-item"><span class="gvk"><span class="k">SuccessPolicy</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#successpolicyrule-v1-batch" class="nav-item"><span class="gvk"><span class="k">SuccessPolicyRule</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#sysctl-v1-core" class="nav-item"><span class="gvk"><span class="k">Sysctl</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#tcpsocketaction-v1-core" class="nav-item"><span class="gvk"><span class="k">TCPSocketAction</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#taint-v1-core" class="nav-item"><span class="gvk"><span class="k">Taint</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#time-v1-meta" class="nav-item"><span class="gvk"><span class="k">Time</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#toleration-v1-core" class="nav-item"><span class="gvk"><span class="k">Toleration</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#topologyselectorlabelrequirement-v1-core" class="nav-item"><span class="gvk"><span class="k">TopologySelectorLabelRequirement</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#topologyselectorterm-v1-core" class="nav-item"><span class="gvk"><span class="k">TopologySelectorTerm</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#topologyspreadconstraint-v1-core" class="nav-item"><span class="gvk"><span class="k">TopologySpreadConstraint</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#typechecking-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">TypeChecking</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#typedlocalobjectreference-v1-core" class="nav-item"><span class="gvk"><span class="k">TypedLocalObjectReference</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#typedobjectreference-v1-core" class="nav-item"><span class="gvk"><span class="k">TypedObjectReference</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#uncountedterminatedpods-v1-batch" class="nav-item"><span class="gvk"><span class="k">UncountedTerminatedPods</span> <span class="v">v1</span> <span class="g">batch</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#userinfo-v1-authentication-k8s-io" class="nav-item"><span class="gvk"><span class="k">UserInfo</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#usersubject-v1-flowcontrol-apiserver-k8s-io" class="nav-item"><span class="gvk"><span class="k">UserSubject</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#validatingwebhook-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ValidatingWebhook</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#validation-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">Validation</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#validationrule-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">ValidationRule</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#variable-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">Variable</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#volumeattachmentsource-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">VolumeAttachmentSource</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#volumedevice-v1-core" class="nav-item"><span class="gvk"><span class="k">VolumeDevice</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#volumeerror-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">VolumeError</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#volumemount-v1-core" class="nav-item"><span class="gvk"><span class="k">VolumeMount</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#volumenodeaffinity-v1-core" class="nav-item"><span class="gvk"><span class="k">VolumeNodeAffinity</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#volumenoderesources-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">VolumeNodeResources</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#volumeprojection-v1-core" class="nav-item"><span class="gvk"><span class="k">VolumeProjection</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#volumeresourcerequirements-v1-core" class="nav-item"><span class="gvk"><span class="k">VolumeResourceRequirements</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#vspherevirtualdiskvolumesource-v1-core" class="nav-item"><span class="gvk"><span class="k">VsphereVirtualDiskVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#watchevent-v1-meta" class="nav-item"><span class="gvk"><span class="k">WatchEvent</span> <span class="v">v1</span> <span class="g">meta</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#webhookclientconfig-v1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">WebhookClientConfig</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#webhookconversion-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">WebhookConversion</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#weightedpodaffinityterm-v1-core" class="nav-item"><span class="gvk"><span class="k">WeightedPodAffinityTerm</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#windowssecuritycontextoptions-v1-core" class="nav-item"><span class="gvk"><span class="k">WindowsSecurityContextOptions</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
</UL>
</LI>
<LI class="nav-level level-1 has-children" data-level="1">
<A href="#old-api-versions" class="nav-item">OLD API VERSIONS</A>
<UL id="old-api-versions-nav">
<LI class="nav-level level-2" data-level="2">
<A href="#allocateddevicestatus-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">AllocatedDeviceStatus</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#allocationresult-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">AllocationResult</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#auditannotation-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">AuditAnnotation</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#basicdevice-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">BasicDevice</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#celdeviceselector-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">CELDeviceSelector</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#crossversionobjectreference-v1-autoscaling" class="nav-item"><span class="gvk"><span class="k">CrossVersionObjectReference</span> <span class="v">v1</span> <span class="g">autoscaling</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#device-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">Device</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceallocationconfiguration-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceAllocationConfiguration</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceallocationresult-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceAllocationResult</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceattribute-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceAttribute</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceclaim-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceClaim</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceclaimconfiguration-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceClaimConfiguration</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#deviceclass-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceClass</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
<UL id="deviceclass-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-deviceclass-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-deviceclass-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-deviceclass-v1alpha3-resource-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceclassconfiguration-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceClassConfiguration</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceconstraint-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceConstraint</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#devicerequest-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceRequest</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#devicerequestallocationresult-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceRequestAllocationResult</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#deviceselector-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">DeviceSelector</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#endpointport-v1-discovery-k8s-io" class="nav-item"><span class="gvk"><span class="k">EndpointPort</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#event-v1-core" class="nav-item"><span class="gvk"><span class="k">Event</span> <span class="v">v1</span> <span class="g">core</span></span></A>
<UL id="event-v1-core-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-event-v1-core" class="nav-item">Write Operations</A>
<UL id="write-operations-event-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-event-v1-core" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-event-v1-core" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-event-v1-core" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-event-v1-core" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-event-v1-core" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-event-v1-core" class="nav-item">Read Operations</A>
<UL id="read-operations-event-v1-core-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-event-v1-core" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-event-v1-core" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-event-v1-core" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-event-v1-core" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-event-v1-core" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-event-v1-core" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#eventseries-v1-core" class="nav-item"><span class="gvk"><span class="k">EventSeries</span> <span class="v">v1</span> <span class="g">core</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#expressionwarning-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ExpressionWarning</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#horizontalpodautoscaler-v1-autoscaling" class="nav-item"><span class="gvk"><span class="k">HorizontalPodAutoscaler</span> <span class="v">v1</span> <span class="g">autoscaling</span></span></A>
<UL id="horizontalpodautoscaler-v1-autoscaling-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Write Operations</A>
<UL id="write-operations-horizontalpodautoscaler-v1-autoscaling-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Read Operations</A>
<UL id="read-operations-horizontalpodautoscaler-v1-autoscaling-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-horizontalpodautoscaler-v1-autoscaling" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-horizontalpodautoscaler-v1-autoscaling" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Status Operations</A>
<UL id="status-operations-horizontalpodautoscaler-v1-autoscaling-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#matchcondition-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MatchCondition</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#matchcondition-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MatchCondition</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#matchresources-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MatchResources</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#matchresources-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">MatchResources</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#namedrulewithoperations-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">NamedRuleWithOperations</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#namedrulewithoperations-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">NamedRuleWithOperations</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#networkdevicedata-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">NetworkDeviceData</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#opaquedeviceconfiguration-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">OpaqueDeviceConfiguration</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#paramkind-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ParamKind</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#paramkind-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ParamKind</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#paramref-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ParamRef</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#paramref-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ParamRef</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#resourceclaim-v1beta1-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceClaim</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></A>
<UL id="resourceclaim-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-resourceclaim-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-resourceclaim-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-resourceclaim-v1beta1-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-resourceclaim-v1beta1-resource-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#resourceclaim-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceClaim</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
<UL id="resourceclaim-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-resourceclaim-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-resourceclaim-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-resourceclaim-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-resourceclaim-v1alpha3-resource-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourceclaimconsumerreference-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceClaimConsumerReference</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceClaimTemplate</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
<UL id="resourceclaimtemplate-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-resourceclaimtemplate-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-resourceclaimtemplate-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-all-namespaces-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">List All Namespaces</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Watch List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-all-namespaces-resourceclaimtemplate-v1alpha3-resource-k8s-io" class="nav-item">Watch List All Namespaces</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#resourcepool-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourcePool</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#resourceslice-v1alpha3-resource-k8s-io" class="nav-item"><span class="gvk"><span class="k">ResourceSlice</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></A>
<UL id="resourceslice-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-resourceslice-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-resourceslice-v1alpha3-resource-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-resourceslice-v1alpha3-resource-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#selfsubjectreview-v1beta1-authentication-k8s-io" class="nav-item"><span class="gvk"><span class="k">SelfSubjectReview</span> <span class="v">v1beta1</span> <span class="g">authentication.k8s.io</span></span></A>
<UL id="selfsubjectreview-v1beta1-authentication-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-selfsubjectreview-v1beta1-authentication-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-selfsubjectreview-v1beta1-authentication-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-selfsubjectreview-v1beta1-authentication-k8s-io" class="nav-item">Create</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#servicereference-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">ServiceReference</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#servicereference-v1-apiregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ServiceReference</span> <span class="v">v1</span> <span class="g">apiregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#subject-v1-rbac-authorization-k8s-io" class="nav-item"><span class="gvk"><span class="k">Subject</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#tokenrequest-v1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">TokenRequest</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#typechecking-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">TypeChecking</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ValidatingAdmissionPolicy</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
<UL id="validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#status-operations-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Status Operations</A>
<UL id="status-operations-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#patch-status-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Patch Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#read-status-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Read Status</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-status-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io" class="nav-item">Replace Status</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">ValidatingAdmissionPolicyBinding</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
<UL id="validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#validation-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">Validation</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#variable-v1beta1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">Variable</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#variable-v1alpha1-admissionregistration-k8s-io" class="nav-item"><span class="gvk"><span class="k">Variable</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></A>
</LI>
<LI class="nav-level level-2 has-children" data-level="2">
<A href="#volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item"><span class="gvk"><span class="k">VolumeAttributesClass</span> <span class="v">v1alpha1</span> <span class="g">storage.k8s.io</span></span></A>
<UL id="volumeattributesclass-v1alpha1-storage-k8s-io-nav">
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#write-operations-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Write Operations</A>
<UL id="write-operations-volumeattributesclass-v1alpha1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#create-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Create</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#patch-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Patch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#replace-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Replace</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Delete</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#delete-collection-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Delete Collection</A>
</LI>
</UL>
</LI>
<LI class="nav-level level-3 has-children" data-level="3">
<A href="#read-operations-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Read Operations</A>
<UL id="read-operations-volumeattributesclass-v1alpha1-storage-k8s-io-nav">
<LI class="nav-level level-4" data-level="4">
<A href="#read-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Read</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#list-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">List</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Watch</A>
</LI>
<LI class="nav-level level-4" data-level="4">
<A href="#watch-list-volumeattributesclass-v1alpha1-storage-k8s-io" class="nav-item">Watch List</A>
</LI>
</UL>
</LI>
</UL>
</LI>
<LI class="nav-level level-2" data-level="2">
<A href="#webhookclientconfig-v1-apiextensions-k8s-io" class="nav-item"><span class="gvk"><span class="k">WebhookClientConfig</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></A>
</LI>
</UL>
</LI>
</UL>
</DIV>
<DIV id="page-content-wrapper" class="col-xs-8 offset-xs-4 col-sm-9 offset-sm-3 col-md-10 offset-md-2 body-content">
<DIV class="row">
<DIV class="col-md-6 copyright">
<a href="https://github.com/kubernetes/kubernetes">Copyright 2016-2024 The Kubernetes Authors.</a>
</DIV>
<DIV class="col-md-6 text-right">
<DIV>Generated at: 2024-12-12 20:52:59 (CST)</DIV>
<DIV>API Version: <a href="https://github.com/kubernetes/kubernetes/blob/release-1.32/api/openapi-spec/swagger.json">v1.32.0</a>
<A href="#" class="btn btn-info btn-sm switch-theme">Switch <I class="fa fa-sun-o"></I>/<I class="fa fa-moon-o"></I></A>
</DIV>
</DIV>
</DIV><DIV id="api-overview">
<H1 class="toc-item section">API Overview</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><STRONG>Workloads</STRONG> are objects you use to manage and run your containers on the cluster.</P>
<P><STRONG>Discovery &amp; LB</STRONG> resources are objects you use to "stitch" your workloads together into an externally accessible, load-balanced Service.</P>
<P><STRONG>Config &amp; Storage</STRONG> resources are objects you use to inject initialization data into your applications, and to persist data that is external to your container.</P>
<P><STRONG>Cluster</STRONG> resources objects define how the cluster itself is configured; these are typically used only by cluster operators.</P>
<P><STRONG>Metadata</STRONG> resources are objects you use to configure the behavior of other resources within the cluster, such as <code>HorizontalPodAutoscaler</code> for scaling workloads.</P>
<H2 id="resource-objects">Resource Objects</H2>
<P>Resource objects typically have 3 components:</P>
<UL>
<LI><STRONG>Resource ObjectMeta</STRONG>: 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><STRONG>ResourceSpec</STRONG>: This is defined by the user and describes the desired state of system. Fill this in when creating or updating an object.</LI>
<LI><STRONG>ResourceStatus</STRONG>: 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>
<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: <STRONG>Replace</STRONG> and <STRONG>Patch</STRONG>:
<UL>
<LI><STRONG>Replace</STRONG>:
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. <EM>Note</EM>: The <EM>ResourceStatus</EM> 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 <EM>Pod</EM>s seeing the changes unless the <EM>Pod</EM>s are
restarted out of band.</LI>
<LI><STRONG>Patch</STRONG>:
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 />
<STRONG>Patches will never cause optimistic locking failures, and the last write will win.</STRONG> Patches are recommended
when the full state is not read before an update, or when failing on optimistic locking is undesirable. <EM>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.</EM></LI>
</UL>
<H4 id="resource-operations-read">Read</H4>
<P>Reads come in 3 forms: <STRONG>Get</STRONG>, <STRONG>List</STRONG> and <STRONG>Watch</STRONG>:</P>
<UL>
<LI><STRONG>Get</STRONG>: Get will retrieve a specific resource object by name.</LI>
<LI><STRONG>List</STRONG>: 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 />
<STRONG>List All Namespaces</STRONG>: Like <STRONG>List</STRONG> but retrieves resources across all namespaces.</LI>
<LI><STRONG>Watch</STRONG>: 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-delete">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><STRONG>Rollback</STRONG>: Rollback a PodTemplate to a previous version. Only available for some resource types.</LI>
<LI><STRONG>Read / Write Scale</STRONG>: Read or Update the number of replicas for the given resource. Only available for some resource types.</LI>
<LI><STRONG>Read / Write Status</STRONG>: Read or Update the Status for a resource object. The Status can only changed through these update operations.</LI>
</UL>
</DIV>
<DIV id="api-groups">
<H1 class="toc-item section">API Groups</H1>
<P>The API Groups and their versions are summarized in the following table.</P>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Versions</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1, v1beta1, v1alpha1</CODE></TD></TR>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2, v1</CODE></TD></TR>
<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>certificates.k8s.io</CODE></TD><TD><CODE>v1, v1alpha1</CODE></TD></TR>
<TR><TD><CODE>coordination.k8s.io</CODE></TD><TD><CODE>v1, v1alpha2</CODE></TD></TR>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>internal.apiserver.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD></TR>
<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1, v1beta1</CODE></TD></TR>
<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1, v1alpha3</CODE></TD></TR>
<TR><TD><CODE>scheduling.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD></TR>
<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1, v1beta1, v1alpha1</CODE></TD></TR>
<TR><TD><CODE>storagemigration.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV id="workloads-apis">
<H1 class="toc-item section resource-category">Workloads</H1>
<P>Workloads resources are responsible for managing and running your containers on the cluster. <A href="#container-v1-core">Containers</A> are created
by Controllers through <A href="#pod-v1-core">Pods</A>. Pods run Containers and provide environmental dependencies such as shared or
persistent storage <A href="#volume-v1-core">Volumes</A> and <A href="#configmap-v1-core">Configuration</A> or <A href="#secret-v1-core">Secret</A>
data injected into the container.</P>
<P>The most common Controllers are:</P>
<UL>
<LI><A href="#deployment-v1-apps">Deployments</A> for stateless persistent apps (e.g. HTTP servers).</LI>
<LI><A href="#statefulset-v1-apps">StatefulSets</A> for stateful persistent apps (e.g. databases).</LI>
<LI><A href="#job-v1-batch">Jobs</A> for run-to-completion apps (e.g. batch Jobs).</LI>
</UL>
</DIV>
<DIV class="resource-container" id="container-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Container</span> <span class="v">v1</span> <span class="g">core</span></span></H1>
<DIV class="samples-container">
<P>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-target="#example-container-v1-core" aria-controls="example-container-v1-core"
aria-expanded="false">show example</BUTTON>
</P>
<DIV class="collapse" id="example-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="example"><CODE class="lang-yaml">name: nginx
# Run the nginx:1.14 image
image: nginx:1.14</CODE></PRE></DIV></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-v1-apps">Deployment</a>, <a href="#job-v1-batch">Job</a>, or <a href="#statefulset-v1-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 container 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. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. 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 container 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. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. 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>Container 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. 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. Modifying this array with strategic merge patch may corrupt the data. For more information See https://github.com/kubernetes/kubernetes/issues/108255. 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>resizePolicy</CODE><BR /><I><a href="#containerresizepolicy-v1-core">ContainerResizePolicy</a> array</I></TD><TD>Resources resize policy for the container.</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/configuration/manage-resources-containers/</TD></TR>
<TR><TD><CODE>restartPolicy</CODE><BR /><I>string</I></TD><TD>RestartPolicy defines the restart behavior of individual containers in a pod. This field may only be set for init containers, and the only allowed value is &#34;Always&#34;. For non-init containers or when this field is not specified, the restart behavior is defined by the Pod&#39;s restart policy and the container type. Setting the RestartPolicy as &#34;Always&#34; for the init container will have the following effect: this init container will be continually restarted on exit until all regular containers have terminated. Once all regular containers have completed, all init containers with restartPolicy &#34;Always&#34; will be shut down. This lifecycle differs from normal init containers and is often referred to as a &#34;sidecar&#34; container. Although this init container still starts in the init container sequence, it does not wait for the container to complete before proceeding to the next init container. Instead, the next init container starts immediately after this init container is started, or after any startupProbe has successfully completed.</TD></TR>
<TR><TD><CODE>securityContext</CODE><BR /><I><a href="#securitycontext-v1-core">SecurityContext</a></I></TD><TD>SecurityContext defines the security options the container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/</TD></TR>
<TR><TD><CODE>startupProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>StartupProbe indicates that the Pod has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod&#39;s lifecycle, when it might take a long time to load data or warm a cache, than during steady-state operation. This cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</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.</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>allocatedResources</CODE><BR /><I>object</I></TD><TD>AllocatedResources represents the compute resources allocated for this container by the node. Kubelet sets this value to Container.Resources.Requests upon successful pod admission and after successfully admitting desired pod resize.</TD></TR>
<TR><TD><CODE>allocatedResourcesStatus</CODE><BR /><I><a href="#resourcestatus-v1-core">ResourceStatus</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>AllocatedResourcesStatus represents the status of various resources allocated for this Pod.</TD></TR>
<TR><TD><CODE>containerID</CODE><BR /><I>string</I></TD><TD>ContainerID is the ID of the container in the format &#39;&lt;type&gt;://&lt;container_id&gt;&#39;. Where type is a container runtime identifier, returned from Version call of CRI API (for example &#34;containerd&#34;).</TD></TR>
<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>Image is the name of container image that the container is running. The container image may not match the image used in the PodSpec, as it may have been resolved by the runtime. More info: https://kubernetes.io/docs/concepts/containers/images.</TD></TR>
<TR><TD><CODE>imageID</CODE><BR /><I>string</I></TD><TD>ImageID is the image ID of the container&#39;s image. The image ID may not match the image ID of the image used in the PodSpec, as it may have been resolved by the runtime.</TD></TR>
<TR><TD><CODE>lastState</CODE><BR /><I><a href="#containerstate-v1-core">ContainerState</a></I></TD><TD>LastTerminationState holds the last termination state of the container to help debug container crashes and restarts. This field is not populated if the container is still running and RestartCount is 0.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is a DNS_LABEL representing the unique name of the container. Each container in a pod must have a unique name across all container types. Cannot be updated.</TD></TR>
<TR><TD><CODE>ready</CODE><BR /><I>boolean</I></TD><TD>Ready specifies whether the container is currently passing its readiness check. The value will change as readiness probes keep executing. If no readiness probes are specified, this field defaults to true once the container is fully started (see Started field). The value is typically used to determine whether a container is ready to accept traffic.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcerequirements-v1-core">ResourceRequirements</a></I></TD><TD>Resources represents the compute resource requests and limits that have been successfully enacted on the running container after it has been started or has been successfully resized.</TD></TR>
<TR><TD><CODE>restartCount</CODE><BR /><I>integer</I></TD><TD>RestartCount holds the number of times the container has been restarted. Kubelet makes an effort to always increment the value, but there are cases when the state may be lost due to node restarts and then the value may be reset to 0. The value is never negative.</TD></TR>
<TR><TD><CODE>started</CODE><BR /><I>boolean</I></TD><TD>Started indicates whether the container has finished its postStart lifecycle hook and passed its startup probe. Initialized as false, becomes true after startupProbe is considered successful. Resets to false when the container is restarted, or if kubelet loses state temporarily. In both cases, startup probes will run again. Is always true when no startupProbe is defined and container is running and has passed the postStart lifecycle hook. The null value must be treated the same as false.</TD></TR>
<TR><TD><CODE>state</CODE><BR /><I><a href="#containerstate-v1-core">ContainerState</a></I></TD><TD>State holds details about the container&#39;s current condition.</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I><a href="#containeruser-v1-core">ContainerUser</a></I></TD><TD>User represents user identity information initially attached to the first process of the container</TD></TR>
<TR><TD><CODE>volumeMounts</CODE><BR /><I><a href="#volumemountstatus-v1-core">VolumeMountStatus</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>mountPath</I></TD><TD>Status of volume mounts.</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
<DIV class="resource-container" id="cronjob-v1-batch">
<H1 class="toc-item resource"><span class="gvk"><span class="k">CronJob</span> <span class="v">v1</span> <span class="g">batch</span></span></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>v1</CODE></TD><TD><CODE>CronJob</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="#cronjoblist-v1-batch">CronJobList [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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#cronjobspec-v1-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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#cronjobstatus-v1-batch">CronJobStatus</a></I></TD><TD>Current status of a cron job. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="cronjobspec-v1-batch">CronJobSpec v1 batch</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjob-v1-batch">CronJob [batch/v1]</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. Value must be non-negative integer. Defaults to 1.</TD></TR>
<TR><TD><CODE>jobTemplate</CODE><BR /><I><a href="#jobtemplatespec-v1-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. Value must be non-negative integer. 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>
<TR><TD><CODE>timeZone</CODE><BR /><I>string</I></TD><TD>The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. The set of valid time zone names and the time zone offset is loaded from the system-wide time zone database by the API server during CronJob validation and the controller manager during execution. If no system-wide time zone database can be found a bundled version of the database is used instead. If the time zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone. More information can be found in https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="cronjobstatus-v1-batch">CronJobStatus v1 batch</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjob-v1-batch">CronJob [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><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>
<TR><TD><CODE>lastSuccessfulTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Information when was the last time the job successfully completed.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="cronjoblist-v1-batch">CronJobList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#cronjob-v1-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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-cronjob-v1-batch">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-cronjob-v1-batch">
<H2 class="toc-item operation">Create</H2>
<P>create a CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/batch/v1/namespaces/{namespace}/cronjobs</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-cronjob-v1-batch">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-cronjob-v1-batch">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-cronjob-v1-batch">
<H2 class="toc-item operation">Delete</H2>
<P>delete a CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-cronjob-v1-batch">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/batch/v1/namespaces/{namespace}/cronjobs</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-cronjob-v1-batch">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-cronjob-v1-batch">
<H2 class="toc-item operation">Read</H2>
<P>read the specified CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-cronjob-v1-batch">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/namespaces/{namespace}/cronjobs</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-cronjob-v1-batch">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/cronjobs</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-cronjob-v1-batch">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind CronJob. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/cronjobs/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-cronjob-v1-batch">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of CronJob. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/cronjobs</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-cronjob-v1-batch">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of CronJob. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/watch/cronjobs</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-cronjob-v1-batch">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-cronjob-v1-batch">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-cronjob-v1-batch">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-cronjob-v1-batch">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified CronJob</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/batch/v1/namespaces/{namespace}/cronjobs/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#cronjob-v1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="daemonset-v1-apps">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DaemonSet</span> <span class="v">v1</span> <span class="g">apps</span></span></H1>
<DIV class="samples-container">
<P>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-target="#example-daemonset-v1-apps" aria-controls="example-daemonset-v1-apps"
aria-expanded="false">show example</BUTTON>
</P>
<DIV class="collapse" id="example-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="example"><CODE class="lang-yaml">apiVersion: apps/v1
kind: DaemonSet
metadata:
# Unique key of the DaemonSet instance
name: daemonset-example
spec:
selector:
matchLabels:
app: daemonset-example
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>
<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-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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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). The only allowed template.spec.restartPolicy value is &#34;Always&#34;. 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 class="inline-definition" 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>numberReady is the number of nodes that should be running the daemon pod and have one or more of the daemon pod running with a Ready Condition.</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 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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>maxSurge</CODE></TD><TD>The maximum number of nodes with an existing available DaemonSet pod that can have an updated DaemonSet pod during during an update. 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 to a minimum of 1. Default value is 0. 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 a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason (Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that node without considering surge limits. Allowing surge implies the possibility that the resources consumed by the daemonset on any given node can double if the readiness check fails, and so resource intensive daemonsets should take into account that they may cause evictions during disruption.</TD></TR>
<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 if MaxSurge is 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>
</DIV>
<DIV class="operation-category-container" id="write-operations-daemonset-v1-apps">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-daemonset-v1-apps">
<H2 class="toc-item operation">Create</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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: apps/v1
kind: DaemonSet
metadata:
name: daemonset-example
spec:
selector:
matchLabels:
app: daemonset-example
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: apps/v1
kind: DaemonSet
metadata:
name: daemonset-example
spec:
selector:
matchLabels:
app: daemonset-example
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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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": "apps/v1",
"metadata": {
"name": "daemonset-example",
"namespace": "default",
"selfLink": "/apis/apps/v1/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>
<p><CODE>POST /apis/apps/v1/namespaces/{namespace}/daemonsets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-daemonset-v1-apps">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified DaemonSet</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-daemonset-v1-apps">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified DaemonSet</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-daemonset-v1-apps">
<H2 class="toc-item operation">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-daemonset-v1-apps">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of DaemonSet</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/daemonsets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-daemonset-v1-apps">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-daemonset-v1-apps">
<H2 class="toc-item operation">Read</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-daemonset-v1-apps">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind DaemonSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/daemonsets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-daemonset-v1-apps">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind DaemonSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/daemonsets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-daemonset-v1-apps">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind DaemonSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/daemonsets/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-daemonset-v1-apps">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of DaemonSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/daemonsets</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-daemonset-v1-apps">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of DaemonSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/daemonsets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-daemonset-v1-apps">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-daemonset-v1-apps">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-daemonset-v1-apps">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-daemonset-v1-apps">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="deployment-v1-apps">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Deployment</span> <span class="v">v1</span> <span class="g">apps</span></span></H1>
<DIV class="samples-container">
<P>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-target="#example-deployment-v1-apps" aria-controls="example-deployment-v1-apps"
aria-expanded="false">show example</BUTTON>
</P>
<DIV class="collapse" id="example-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="example"><CODE class="lang-yaml">apiVersion: apps/v1
kind: Deployment
metadata:
# Unique key of the Deployment instance
name: deployment-example
spec:
# 3 Pods should exist at all times.
replicas: 3
selector:
matchLabels:
app: nginx
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.14</CODE></PRE></DIV></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-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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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><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. The only allowed template.spec.restartPolicy value is &#34;Always&#34;.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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>readyReplicas is the number of pods targeted by this Deployment with a Ready Condition.</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 class="inline-definition" 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/sig-architecture/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/sig-architecture/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 class="inline-definition" 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 class="inline-definition" 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>
</DIV>
<DIV class="operation-category-container" id="write-operations-deployment-v1-apps">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-deployment-v1-apps">
<H2 class="toc-item operation">Create</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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/v1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.14
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/v1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.14
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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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/v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1/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.14",
"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>
<p><CODE>POST /apis/apps/v1/namespaces/{namespace}/deployments</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-deployment-v1-apps">
<H2 class="toc-item operation">Patch</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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.16"}]}}}}'</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.16"}]}}}}' \
'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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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/v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1/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.16",
"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>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-deployment-v1-apps">
<H2 class="toc-item operation">Replace</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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/v1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.16
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/v1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.16
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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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/v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1/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.16",
"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>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-deployment-v1-apps">
<H2 class="toc-item operation">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-deployment-v1-apps">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Deployment</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/deployments</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-deployment-v1-apps">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-deployment-v1-apps">
<H2 class="toc-item operation">Read</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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/v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1/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.14",
"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/v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1/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.14",
"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>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-deployment-v1-apps">
<H2 class="toc-item operation">List</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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.14",
"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.14",
"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>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-deployment-v1-apps">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Deployment</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/deployments</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-deployment-v1-apps">
<H2 class="toc-item operation">Watch</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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/v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1/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.14",
"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/v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1/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.14",
"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. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/deployments/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-deployment-v1-apps">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Deployment. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/deployments</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-deployment-v1-apps">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Deployment. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/deployments</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-deployment-v1-apps">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-deployment-v1-apps">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified Deployment</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-deployment-v1-apps">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified Deployment</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-deployment-v1-apps">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified Deployment</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/deployments/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="misc-operations-deployment-v1-apps">
<H2 class="toc-item operation-category">Misc Operations</H2>
<DIV class="operation-container" id="read-scale-deployment-v1-apps">
<H2 class="toc-item operation">Read Scale</H2>
<P>read scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-scale-deployment-v1-apps">
<H2 class="toc-item operation">Replace Scale</H2>
<P>replace scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-scale-deployment-v1-apps">
<H2 class="toc-item operation">Patch Scale</H2>
<P>partially update scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="job-v1-batch">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Job</span> <span class="v">v1</span> <span class="g">batch</span></span></H1>
<DIV class="samples-container">
<P>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-target="#example-job-v1-batch" aria-controls="example-job-v1-batch"
aria-expanded="false">show example</BUTTON>
</P>
<DIV class="collapse" id="example-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="example"><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>
<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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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-v1-batch">JobTemplateSpec [batch/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>Specifies the duration in seconds relative to the startTime that the job may be continuously active before the system tries to terminate it; value must be positive integer. If a Job is suspended (at creation or through an update), this timer will effectively be stopped and reset when the Job is resumed again.</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>backoffLimitPerIndex</CODE><BR /><I>integer</I></TD><TD>Specifies the limit for the number of retries within an index before marking this index as failed. When enabled the number of failures per index is kept in the pod&#39;s batch.kubernetes.io/job-index-failure-count annotation. It can only be set when Job&#39;s completionMode=Indexed, and the Pod&#39;s restart policy is Never. The field is immutable. This field is beta-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (enabled by default).</TD></TR>
<TR><TD><CODE>completionMode</CODE><BR /><I>string</I></TD><TD>completionMode specifies how Pod completions are tracked. It can be `NonIndexed` (default) or `Indexed`. `NonIndexed` means that the Job is considered complete when there have been .spec.completions successfully completed Pods. Each Pod completion is homologous to each other. `Indexed` means that the Pods of a Job get an associated completion index from 0 to (.spec.completions - 1), available in the annotation batch.kubernetes.io/job-completion-index. The Job is considered complete when there is one successfully completed Pod for each index. When value is `Indexed`, .spec.completions must be specified and `.spec.parallelism` must be less than or equal to 10^5. In addition, The Pod name takes the form `$(job-name)-$(index)-$(random-string)`, the Pod hostname takes the form `$(job-name)-$(index)`. More completion modes can be added in the future. If the Job controller observes a mode that it doesn&#39;t recognize, which is possible during upgrades due to version skew, the controller skips updates for the Job.</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 null 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>managedBy</CODE><BR /><I>string</I></TD><TD>ManagedBy field indicates the controller that manages a Job. The k8s Job controller reconciles jobs which don&#39;t have this field at all or the field value is the reserved string `kubernetes.io/job-controller`, but skips reconciling Jobs with a custom value for this field. The value must be a valid domain-prefixed path (e.g. acme.io/foo) - all characters before the first &#34;/&#34; must be a valid subdomain as defined by RFC 1123. All characters trailing the first &#34;/&#34; must be valid HTTP Path characters as defined by RFC 3986. The value cannot exceed 63 characters. This field is immutable. This field is beta-level. The job controller accepts setting the field when the feature gate JobManagedBy is enabled (enabled by default).</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>maxFailedIndexes</CODE><BR /><I>integer</I></TD><TD>Specifies the maximal number of failed indexes before marking the Job as failed, when backoffLimitPerIndex is set. Once the number of failed indexes exceeds this number the entire Job is marked as Failed and its execution is terminated. When left as null the job continues execution of all of its indexes and is marked with the `Complete` Job condition. It can only be specified when backoffLimitPerIndex is set. It can be null or up to completions. It is required and must be less than or equal to 10^4 when is completions greater than 10^5. This field is beta-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (enabled by default).</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>podFailurePolicy</CODE><BR /><I><a href="#podfailurepolicy-v1-batch">PodFailurePolicy</a></I></TD><TD>Specifies the policy of handling failed pods. In particular, it allows to specify the set of actions and conditions which need to be satisfied to take the associated action. If empty, the default behaviour applies - the counter of failed pods, represented by the jobs&#39;s .status.failed field, is incremented and it is checked against the backoffLimit. This field cannot be used in combination with restartPolicy=OnFailure.</TD></TR>
<TR><TD><CODE>podReplacementPolicy</CODE><BR /><I>string</I></TD><TD>podReplacementPolicy specifies when to create replacement Pods. Possible values are: - TerminatingOrFailed means that we recreate pods when they are terminating (has a metadata.deletionTimestamp) or failed. - Failed means to wait until a previously created Pod is fully terminated (has phase Failed or Succeeded) before creating a replacement Pod. When using podFailurePolicy, Failed is the the only allowed value. TerminatingOrFailed and Failed are allowed values when podFailurePolicy is not in use. This is an beta field. To use this, enable the JobPodReplacementPolicy feature toggle. This is on by default.</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>successPolicy</CODE><BR /><I><a href="#successpolicy-v1-batch">SuccessPolicy</a></I></TD><TD>successPolicy specifies the policy when the Job can be declared as succeeded. If empty, the default behavior applies - the Job is declared as succeeded only when the number of succeeded pods equals to the completions. When the field is specified, it must be immutable and works only for the Indexed Jobs. Once the Job meets the SuccessPolicy, the lingering pods are terminated. This field is beta-level. To use this field, you must enable the `JobSuccessPolicy` feature gate (enabled by default).</TD></TR>
<TR><TD><CODE>suspend</CODE><BR /><I>boolean</I></TD><TD>suspend specifies whether the Job controller should create Pods or not. If a Job is created with suspend set to true, no Pods are created by the Job controller. If a Job is suspended after creation (i.e. the flag goes from false to true), the Job controller will delete all active Pods associated with this Job. Users must design their workload to gracefully handle this. Suspending a Job will reset the StartTime field of the Job, effectively resetting the ActiveDeadlineSeconds timer too. Defaults to false.</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. The only allowed template.spec.restartPolicy values are &#34;Never&#34; or &#34;OnFailure&#34;. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/</TD></TR>
<TR><TD><CODE>ttlSecondsAfterFinished</CODE><BR /><I>integer</I></TD><TD>ttlSecondsAfterFinished limits the lifetime of a Job that has finished execution (either Complete or Failed). If this field is set, ttlSecondsAfterFinished after the Job finishes, it is eligible to be automatically deleted. When the Job is being deleted, its lifecycle guarantees (e.g. finalizers) will be honored. If this field is unset, the Job won&#39;t be automatically deleted. If this field is set to zero, the Job becomes eligible to be deleted immediately after it finishes.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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 pending and running pods which are not terminating (without a deletionTimestamp). The value is zero for finished jobs.</TD></TR>
<TR><TD><CODE>completedIndexes</CODE><BR /><I>string</I></TD><TD>completedIndexes holds the completed indexes when .spec.completionMode = &#34;Indexed&#34; in a text format. The indexes are represented as decimal integers separated by commas. The numbers are listed in increasing order. Three or more consecutive numbers are compressed and represented by the first and last element of the series, separated by a hyphen. For example, if the completed indexes are 1, 3, 4, 5 and 7, they are represented as &#34;1,3-5,7&#34;.</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. The completion time is set when the job finishes successfully, and only then. The value cannot be updated or removed. The value indicates the same or later point in time as the startTime field.</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. When a Job fails, one of the conditions will have type &#34;Failed&#34; and status true. When a Job is suspended, one of the conditions will have type &#34;Suspended&#34; and status true; when the Job is resumed, the status of this condition will become false. When a Job is completed, one of the conditions will have type &#34;Complete&#34; and status true. A job is considered finished when it is in a terminal condition, either &#34;Complete&#34; or &#34;Failed&#34;. A Job cannot have both the &#34;Complete&#34; and &#34;Failed&#34; conditions. Additionally, it cannot be in the &#34;Complete&#34; and &#34;FailureTarget&#34; conditions. The &#34;Complete&#34;, &#34;Failed&#34; and &#34;FailureTarget&#34; conditions cannot be disabled. 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. The value increases monotonically.</TD></TR>
<TR><TD><CODE>failedIndexes</CODE><BR /><I>string</I></TD><TD>FailedIndexes holds the failed indexes when spec.backoffLimitPerIndex is set. The indexes are represented in the text format analogous as for the `completedIndexes` field, ie. they are kept as decimal integers separated by commas. The numbers are listed in increasing order. Three or more consecutive numbers are compressed and represented by the first and last element of the series, separated by a hyphen. For example, if the failed indexes are 1, 3, 4, 5 and 7, they are represented as &#34;1,3-5,7&#34;. The set of failed indexes cannot overlap with the set of completed indexes. This field is beta-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (enabled by default).</TD></TR>
<TR><TD><CODE>ready</CODE><BR /><I>integer</I></TD><TD>The number of active pods which have a Ready condition and are not terminating (without a deletionTimestamp).</TD></TR>
<TR><TD><CODE>startTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Represents time when the job controller started processing a job. When a Job is created in the suspended state, this field is not set until the first time it is resumed. This field is reset every time a Job is resumed from suspension. It is represented in RFC3339 form and is in UTC. Once set, the field can only be removed when the job is suspended. The field cannot be modified while the job is unsuspended or finished.</TD></TR>
<TR><TD><CODE>succeeded</CODE><BR /><I>integer</I></TD><TD>The number of pods which reached phase Succeeded. The value increases monotonically for a given spec. However, it may decrease in reaction to scale down of elastic indexed jobs.</TD></TR>
<TR><TD><CODE>terminating</CODE><BR /><I>integer</I></TD><TD>The number of pods which are terminating (in phase Pending or Running and have a deletionTimestamp). This field is beta-level. The job controller populates the field when the feature gate JobPodReplacementPolicy is enabled (enabled by default).</TD></TR>
<TR><TD><CODE>uncountedTerminatedPods</CODE><BR /><I><a href="#uncountedterminatedpods-v1-batch">UncountedTerminatedPods</a></I></TD><TD>uncountedTerminatedPods holds the UIDs of Pods that have terminated but the job controller hasn&#39;t yet accounted for in the status counters. The job controller creates pods with a finalizer. When a pod terminates (succeeded or failed), the controller does three steps to account for it in the job status: 1. Add the pod UID to the arrays in this field. 2. Remove the pod finalizer. 3. Remove the pod UID from the arrays while increasing the corresponding counter. Old jobs might not be tracked using this field, in which case the field remains null. The structure is empty for finished jobs.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-job-v1-batch">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-job-v1-batch">
<H2 class="toc-item operation">Create</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>POST /apis/batch/v1/namespaces/{namespace}/jobs</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-job-v1-batch">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Job</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-job-v1-batch">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Job</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-job-v1-batch">
<H2 class="toc-item operation">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>DELETE /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-job-v1-batch">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Job</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/batch/v1/namespaces/{namespace}/jobs</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-job-v1-batch">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-job-v1-batch">
<H2 class="toc-item operation">Read</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>GET /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-job-v1-batch">
<H2 class="toc-item operation">List</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>GET /apis/batch/v1/namespaces/{namespace}/jobs</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-job-v1-batch">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Job</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/jobs</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-job-v1-batch">
<H2 class="toc-item operation">Watch</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/jobs/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-job-v1-batch">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Job. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/jobs</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-job-v1-batch">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Job. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/watch/jobs</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-job-v1-batch">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-job-v1-batch">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified Job</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-job-v1-batch">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified Job</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-job-v1-batch">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified Job</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="pod-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Pod</span> <span class="v">v1</span> <span class="g">core</span></span></H1>
<DIV class="samples-container">
<P>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-target="#example-pod-v1-core" aria-controls="example-pod-v1-core"
aria-expanded="false">show example</BUTTON>
</P>
<DIV class="collapse" id="example-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="example"><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>
<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-v1-apps">Deployment</a>, <a href="#job-v1-batch">Job</a>, or <a href="#statefulset-v1-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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>enableServiceLinks</CODE><BR /><I>boolean</I></TD><TD>EnableServiceLinks indicates whether information about services should be injected into pod&#39;s environment variables, matching the syntax of Docker links. Optional: Defaults to true.</TD></TR>
<TR><TD><CODE>ephemeralContainers</CODE><BR /><I><a href="#ephemeralcontainer-v1-core">EphemeralContainer</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of ephemeral containers run in this pod. Ephemeral containers may be run in an existing pod to perform user-initiated actions such as debugging. This list cannot be specified when creating a pod, and it cannot be modified by updating the pod spec. In order to add an ephemeral container to an existing pod, use the pod&#39;s ephemeralcontainers subresource.</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.</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>hostUsers</CODE><BR /><I>boolean</I></TD><TD>Use the host&#39;s user namespace. Optional: Default to true. If set to true or not present, the pod will be run in the host user namespace, useful for when the pod needs a feature only available to the host user namespace, such as loading a kernel module with CAP_SYS_MODULE. When set to false, a new userns is created for the pod. Setting false is useful for mitigating container breakout vulnerabilities even allowing users to run their containers as root without actually having root privileges on the host. This field is alpha-level and is only honored by servers that enable the UserNamespacesSupport feature.</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. 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, Liveness probes, or Startup 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 indicates in which node this pod is scheduled. If empty, this pod is a candidate for scheduling by the scheduler defined in schedulerName. Once this field is set, the kubelet for this node becomes responsible for the lifecycle of this pod. This field should not be used to express a desire for the pod to be scheduled on a specific node. https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodename</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>os</CODE><BR /><I><a href="#podos-v1-core">PodOS</a></I></TD><TD>Specifies the OS of the containers in the pod. Some pod and container fields are restricted if this is set. If the OS field is set to linux, the following fields must be unset: -securityContext.windowsOptions If the OS field is set to windows, following fields must be unset: - spec.hostPID - spec.hostIPC - spec.hostUsers - spec.securityContext.appArmorProfile - spec.securityContext.seLinuxOptions - spec.securityContext.seccompProfile - spec.securityContext.fsGroup - spec.securityContext.fsGroupChangePolicy - spec.securityContext.sysctls - spec.shareProcessNamespace - spec.securityContext.runAsUser - spec.securityContext.runAsGroup - spec.securityContext.supplementalGroups - spec.securityContext.supplementalGroupsPolicy - spec.containers[*].securityContext.appArmorProfile - spec.containers[*].securityContext.seLinuxOptions - spec.containers[*].securityContext.seccompProfile - spec.containers[*].securityContext.capabilities - spec.containers[*].securityContext.readOnlyRootFilesystem - spec.containers[*].securityContext.privileged - spec.containers[*].securityContext.allowPrivilegeEscalation - spec.containers[*].securityContext.procMount - spec.containers[*].securityContext.runAsUser - spec.containers[*].securityContext.runAsGroup</TD></TR>
<TR><TD><CODE>overhead</CODE><BR /><I>object</I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. This field will be autopopulated at admission time by the RuntimeClass admission controller. If the RuntimeClass admission controller is enabled, overhead must not be set in Pod create requests. The RuntimeClass admission controller will reject Pod create requests which have the overhead already set. If RuntimeClass is configured and selected in the PodSpec, Overhead will be set to the value defined in the corresponding RuntimeClass, otherwise it will remain unset and treated as zero. More info: https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead/README.md</TD></TR>
<TR><TD><CODE>preemptionPolicy</CODE><BR /><I>string</I></TD><TD>PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.</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://git.k8s.io/enhancements/keps/sig-network/580-pod-readiness-gates</TD></TR>
<TR><TD><CODE>resourceClaims</CODE><BR /><I><a href="#podresourceclaim-v1-core">PodResourceClaim</a> array</I><BR /><B>patch strategy</B>: <I>merge,retainKeys</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>ResourceClaims defines which ResourceClaims must be allocated and reserved before the Pod is allowed to start. The resources will be made available to those containers which consume them by name. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcerequirements-v1-core">ResourceRequirements</a></I></TD><TD>Resources is the total amount of CPU and Memory resources required by all containers in the pod. It supports specifying Requests and Limits for &#34;cpu&#34; and &#34;memory&#34; resource names only. ResourceClaims are not supported. This field enables fine-grained control over resource allocation for the entire pod, allowing resource sharing among containers in a pod. This is an alpha field and requires enabling the PodLevelResources feature gate.</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. In some contexts, only a subset of those values may be permitted. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy</TD></TR>
<TR><TD><CODE>runtimeClassName</CODE><BR /><I>string</I></TD><TD>RuntimeClassName refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod. If no RuntimeClass resource matches the named class, the pod will not be run. If unset or empty, the &#34;legacy&#34; RuntimeClass will be used, which is an implicit class with an empty definition that uses the default runtime handler. More info: https://git.k8s.io/enhancements/keps/sig-node/585-runtime-class</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>schedulingGates</CODE><BR /><I><a href="#podschedulinggate-v1-core">PodSchedulingGate</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>SchedulingGates is an opaque list of values that if specified will block scheduling the pod. If schedulingGates is not empty, the pod will stay in the SchedulingGated state and the scheduler will not attempt to schedule the pod. SchedulingGates can only be set at pod creation time, and be removed only afterwards.</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 deprecated 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>setHostnameAsFQDN</CODE><BR /><I>boolean</I></TD><TD>If true the pod&#39;s hostname will be configured as the pod&#39;s FQDN, rather than the leaf name (the default). In Linux containers, this means setting the FQDN in the hostname field of the kernel (the nodename field of struct utsname). In Windows containers, this means setting the registry value of hostname for the registry key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters to FQDN. If a pod does not have FQDN, this has no effect. Default to false.</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.</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 stop immediately via the kill signal (no opportunity to shut down). 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>topologySpreadConstraints</CODE><BR /><I><a href="#topologyspreadconstraint-v1-core">TopologySpreadConstraint</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>topologyKey</I></TD><TD>TopologySpreadConstraints describes how a group of pods ought to spread across topology domains. Scheduler will schedule pods in a way which abides by the constraints. All topologySpreadConstraints are ANDed.</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 class="inline-definition" 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>Statuses of containers in this pod. Each container in the pod should have at most one status in this list, and all statuses should be for containers in the pod. However this is not enforced. If a status for a non-existent container is present in the list, or the list has duplicate names, the behavior of various Kubernetes components is not defined and those statuses might be ignored. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status</TD></TR>
<TR><TD><CODE>ephemeralContainerStatuses</CODE><BR /><I><a href="#containerstatus-v1-core">ContainerStatus</a> array</I></TD><TD>Statuses for any ephemeral containers that have run in this pod. Each ephemeral container in the pod should have at most one status in this list, and all statuses should be for containers in the pod. However this is not enforced. If a status for a non-existent container is present in the list, or the list has duplicate names, the behavior of various Kubernetes components is not defined and those statuses might be ignored. 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>hostIP holds the IP address of the host to which the pod is assigned. Empty if the pod has not started yet. A pod can be assigned to a node that has a problem in kubelet which in turns mean that HostIP will not be updated even if there is a node is assigned to pod</TD></TR>
<TR><TD><CODE>hostIPs</CODE><BR /><I><a href="#hostip-v1-core">HostIP</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>ip</I></TD><TD>hostIPs holds the IP addresses allocated to the host. If this field is specified, the first entry must match the hostIP field. This list is empty if the pod has not started yet. A pod can be assigned to a node that has a problem in kubelet which in turns means that HostIPs will not be updated even if there is a node is assigned to this pod.</TD></TR>
<TR><TD><CODE>initContainerStatuses</CODE><BR /><I><a href="#containerstatus-v1-core">ContainerStatus</a> array</I></TD><TD>Statuses of init containers in this pod. The most recent successful non-restartable init container will have ready = true, the most recently started container will have startTime set. Each init container in the pod should have at most one status in this list, and all statuses should be for containers in the pod. However this is not enforced. If a status for a non-existent container is present in the list, or the list has duplicate names, the behavior of various Kubernetes components is not defined and those statuses might be ignored. 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>podIP address allocated to the pod. Routable at least within the cluster. Empty if not yet allocated.</TD></TR>
<TR><TD><CODE>podIPs</CODE><BR /><I><a href="#podip-v1-core">PodIP</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>ip</I></TD><TD>podIPs holds the IP addresses allocated to the pod. If this field is specified, the 0th entry must match the podIP field. Pods may be allocated at most 1 value for each of IPv4 and IPv6. This list is empty if no IPs have been allocated yet.</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://kubernetes.io/docs/concepts/workloads/pods/pod-qos/#quality-of-service-classes</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>resize</CODE><BR /><I>string</I></TD><TD>Status of resources resize desired for pod&#39;s containers. It is empty if no resources resize is pending. Any changes to container resources will automatically set this to &#34;Proposed&#34;</TD></TR>
<TR><TD><CODE>resourceClaimStatuses</CODE><BR /><I><a href="#podresourceclaimstatus-v1-core">PodResourceClaimStatus</a> array</I><BR /><B>patch strategy</B>: <I>merge,retainKeys</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Status of resource claims.</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 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-pod-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-pod-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a Pod</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/pods</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="create-eviction-pod-v1-core">
<H2 class="toc-item operation">Create Eviction</H2>
<P>create eviction of a Pod</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/eviction</CODE></P>
<H3>Path 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>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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>200<br /><I><a href="#eviction-v1-policy">Eviction</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#eviction-v1-policy">Eviction</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#eviction-v1-policy">Eviction</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-pod-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/pods/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-pod-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-pod-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a Pod</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/pods/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-pod-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/pods</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-pod-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-pod-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-pod-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-pod-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/pods</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-pod-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Pod. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/pods/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-pod-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Pod. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/pods</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-pod-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Pod. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/pods</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-pod-v1-core">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-pod-v1-core">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/pods/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-pod-v1-core">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-pod-v1-core">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="resize-operations-pod-v1-core">
<H2 class="toc-item operation-category">Resize Operations</H2>
<DIV class="operation-container" id="read-resize-pod-v1-core">
<H2 class="toc-item operation">Read Resize</H2>
<P>read resize of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/resize</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="patch-resize-pod-v1-core">
<H2 class="toc-item operation">Patch Resize</H2>
<P>partially update resize of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/pods/{name}/resize</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-resize-pod-v1-core">
<H2 class="toc-item operation">Replace Resize</H2>
<P>replace resize of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/resize</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="ephemeralcontainers-operations-pod-v1-core">
<H2 class="toc-item operation-category">EphemeralContainers Operations</H2>
<DIV class="operation-container" id="patch-ephemeralcontainers-pod-v1-core">
<H2 class="toc-item operation">Patch EphemeralContainers</H2>
<P>partially update ephemeralcontainers of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/pods/{name}/ephemeralcontainers</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-ephemeralcontainers-pod-v1-core">
<H2 class="toc-item operation">Read EphemeralContainers</H2>
<P>read ephemeralcontainers of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/ephemeralcontainers</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-ephemeralcontainers-pod-v1-core">
<H2 class="toc-item operation">Replace EphemeralContainers</H2>
<P>replace ephemeralcontainers of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/ephemeralcontainers</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="proxy-operations-pod-v1-core">
<H2 class="toc-item operation-category">Proxy Operations</H2>
<DIV class="operation-container" id="create-connect-portforward-pod-v1-core">
<H2 class="toc-item operation">Create Connect Portforward</H2>
<P>connect POST requests to portforward of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/portforward</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodPortForwardOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="create-connect-proxy-pod-v1-core">
<H2 class="toc-item operation">Create Connect Proxy</H2>
<P>connect POST requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="create-connect-proxy-path-pod-v1-core">
<H2 class="toc-item operation">Create Connect Proxy Path</H2>
<P>connect POST requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</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>
</DIV>
<DIV class="operation-container" id="delete-connect-proxy-pod-v1-core">
<H2 class="toc-item operation">Delete Connect Proxy</H2>
<P>connect DELETE requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="delete-connect-proxy-path-pod-v1-core">
<H2 class="toc-item operation">Delete Connect Proxy Path</H2>
<P>connect DELETE requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</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>
</DIV>
<DIV class="operation-container" id="get-connect-portforward-pod-v1-core">
<H2 class="toc-item operation">Get Connect Portforward</H2>
<P>connect GET requests to portforward of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/portforward</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodPortForwardOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="get-connect-proxy-pod-v1-core">
<H2 class="toc-item operation">Get Connect Proxy</H2>
<P>connect GET requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="get-connect-proxy-path-pod-v1-core">
<H2 class="toc-item operation">Get Connect Proxy Path</H2>
<P>connect GET requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</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>
</DIV>
<DIV class="operation-container" id="head-connect-proxy-pod-v1-core">
<H2 class="toc-item operation">Head Connect Proxy</H2>
<P>connect HEAD requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>HEAD /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="head-connect-proxy-path-pod-v1-core">
<H2 class="toc-item operation">Head Connect Proxy Path</H2>
<P>connect HEAD requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>HEAD /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</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>
</DIV>
<DIV class="operation-container" id="replace-connect-proxy-pod-v1-core">
<H2 class="toc-item operation">Replace Connect Proxy</H2>
<P>connect PUT requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="replace-connect-proxy-path-pod-v1-core">
<H2 class="toc-item operation">Replace Connect Proxy Path</H2>
<P>connect PUT requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodProxyOptions</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="misc-operations-pod-v1-core">
<H2 class="toc-item operation-category">Misc Operations</H2>
<DIV class="operation-container" id="read-log-pod-v1-core">
<H2 class="toc-item operation">Read Log</H2>
<P>read log of the specified Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/log</CODE></P>
<H3>Path 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>insecureSkipTLSVerifyBackend</CODE></TD><TD>insecureSkipTLSVerifyBackend indicates that the apiserver should not confirm the validity of the serving certificate of the backend it is connecting to. This will make the HTTPS connection between the apiserver and the backend insecure. This means the apiserver cannot verify the log data it is receiving came from the real kubelet. If the kubelet is configured to verify the apiserver's TLS credentials, it does not mean the connection to the real kubelet is vulnerable to a man in the middle attack (e.g. an attacker could not intercept the actual log data coming from the real kubelet).</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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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>stream</CODE></TD><TD>Specify which container log stream to return to the client. Acceptable values are "All", "Stdout" and "Stderr". If not specified, "All" is used, and both stdout and stderr are returned interleaved. Note that when "TailLines" is specified, "Stream" can only be set to nil or "All".</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. Note that when "TailLines" is specified, "Stream" can only be set to nil or "All".</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>
</DIV>
<DIV class="operation-container" id="get-connect-exec-pod-v1-core">
<H2 class="toc-item operation">Get Connect Exec</H2>
<P>connect GET requests to exec of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/exec</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodExecOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>command</CODE></TD><TD>Command is the remote command to execute. argv array. Not executed within a shell.</TD></TR>
<TR><TD><CODE>container</CODE></TD><TD>Container in which to execute the command. Defaults to only container if there is only one container in the pod.</TD></TR>
<TR><TD><CODE>stderr</CODE></TD><TD>Redirect the standard error stream of the pod for this call.</TD></TR>
<TR><TD><CODE>stdin</CODE></TD><TD>Redirect the standard input stream of the pod for this call. Defaults to false.</TD></TR>
<TR><TD><CODE>stdout</CODE></TD><TD>Redirect the standard output stream of the pod for this call.</TD></TR>
<TR><TD><CODE>tty</CODE></TD><TD>TTY if true indicates that a tty will be allocated for the exec call. 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>
</DIV>
<DIV class="operation-container" id="create-connect-exec-pod-v1-core">
<H2 class="toc-item operation">Create Connect Exec</H2>
<P>connect POST requests to exec of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/exec</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodExecOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>command</CODE></TD><TD>Command is the remote command to execute. argv array. Not executed within a shell.</TD></TR>
<TR><TD><CODE>container</CODE></TD><TD>Container in which to execute the command. Defaults to only container if there is only one container in the pod.</TD></TR>
<TR><TD><CODE>stderr</CODE></TD><TD>Redirect the standard error stream of the pod for this call.</TD></TR>
<TR><TD><CODE>stdin</CODE></TD><TD>Redirect the standard input stream of the pod for this call. Defaults to false.</TD></TR>
<TR><TD><CODE>stdout</CODE></TD><TD>Redirect the standard output stream of the pod for this call.</TD></TR>
<TR><TD><CODE>tty</CODE></TD><TD>TTY if true indicates that a tty will be allocated for the exec call. 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>
</DIV>
<DIV class="operation-container" id="get-connect-attach-pod-v1-core">
<H2 class="toc-item operation">Get Connect Attach</H2>
<P>connect GET requests to attach of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/attach</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodAttachOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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 in which to execute the command. Defaults to only container if there is only one container in the pod.</TD></TR>
<TR><TD><CODE>stderr</CODE></TD><TD>Stderr if true indicates that stderr is to be redirected for the attach call. Defaults to true.</TD></TR>
<TR><TD><CODE>stdin</CODE></TD><TD>Stdin if true, redirects the standard input stream of the pod for this call. Defaults to false.</TD></TR>
<TR><TD><CODE>stdout</CODE></TD><TD>Stdout if true indicates that stdout is to be redirected for the attach call. Defaults to true.</TD></TR>
<TR><TD><CODE>tty</CODE></TD><TD>TTY if true indicates that a tty will be allocated for the attach call. This is passed through the container runtime so the tty is allocated on the worker node by the container runtime. 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>
</DIV>
<DIV class="operation-container" id="create-connect-attach-pod-v1-core">
<H2 class="toc-item operation">Create Connect Attach</H2>
<P>connect POST requests to attach of Pod</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/attach</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodAttachOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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 in which to execute the command. Defaults to only container if there is only one container in the pod.</TD></TR>
<TR><TD><CODE>stderr</CODE></TD><TD>Stderr if true indicates that stderr is to be redirected for the attach call. Defaults to true.</TD></TR>
<TR><TD><CODE>stdin</CODE></TD><TD>Stdin if true, redirects the standard input stream of the pod for this call. Defaults to false.</TD></TR>
<TR><TD><CODE>stdout</CODE></TD><TD>Stdout if true indicates that stdout is to be redirected for the attach call. Defaults to true.</TD></TR>
<TR><TD><CODE>tty</CODE></TD><TD>TTY if true indicates that a tty will be allocated for the attach call. This is passed through the container runtime so the tty is allocated on the worker node by the container runtime. 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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="replicaset-v1-apps">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ReplicaSet</span> <span class="v">v1</span> <span class="g">apps</span></span></H1>
<DIV class="samples-container">
<P>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-target="#example-replicaset-v1-apps" aria-controls="example-replicaset-v1-apps"
aria-expanded="false">show example</BUTTON>
</P>
<DIV class="collapse" id="example-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="example"><CODE class="lang-yaml">apiVersion: apps/v1
kind: ReplicaSet
metadata:
# Unique key of the ReplicaSet instance
name: replicaset-example
spec:
# 3 Pods should exist at all times.
replicas: 3
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
# Run the nginx image
- name: nginx
image: nginx:1.14</CODE></PRE></DIV></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-v1-apps">Deployment</a> instead of ReplicaSet.</P></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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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 class="inline-definition" 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>readyReplicas is the number of pods targeted by this ReplicaSet with a Ready Condition.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the most recently observed number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-replicaset-v1-apps">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-replicaset-v1-apps">
<H2 class="toc-item operation">Create</H2>
<P>create a ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/apps/v1/namespaces/{namespace}/replicasets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-replicaset-v1-apps">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-replicaset-v1-apps">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-replicaset-v1-apps">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-replicaset-v1-apps">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/replicasets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-replicaset-v1-apps">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-replicaset-v1-apps">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-replicaset-v1-apps">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-replicaset-v1-apps">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/replicasets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-replicaset-v1-apps">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ReplicaSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/replicasets/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-replicaset-v1-apps">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ReplicaSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/replicasets</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-replicaset-v1-apps">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ReplicaSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/replicasets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-replicaset-v1-apps">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-replicaset-v1-apps">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-replicaset-v1-apps">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-replicaset-v1-apps">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="misc-operations-replicaset-v1-apps">
<H2 class="toc-item operation-category">Misc Operations</H2>
<DIV class="operation-container" id="read-scale-replicaset-v1-apps">
<H2 class="toc-item operation">Read Scale</H2>
<P>read scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-scale-replicaset-v1-apps">
<H2 class="toc-item operation">Replace Scale</H2>
<P>replace scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-scale-replicaset-v1-apps">
<H2 class="toc-item operation">Patch Scale</H2>
<P>partially update scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="replicationcontroller-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ReplicationController</span> <span class="v">v1</span> <span class="g">core</span></span></H1>
<DIV class="samples-container">
<P>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-target="#example-replicationcontroller-v1-core" aria-controls="example-replicationcontroller-v1-core"
aria-expanded="false">show example</BUTTON>
</P>
<DIV class="collapse" id="example-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="example"><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.14</CODE></PRE></DIV></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-v1-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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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. The only allowed template.spec.restartPolicy value is &#34;Always&#34;. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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 observed number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#what-is-a-replicationcontroller</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-replicationcontroller-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-replicationcontroller-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/replicationcontrollers</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-replicationcontroller-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-replicationcontroller-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-replicationcontroller-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-replicationcontroller-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/replicationcontrollers</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-replicationcontroller-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-replicationcontroller-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-replicationcontroller-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-replicationcontroller-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/replicationcontrollers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-replicationcontroller-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ReplicationController. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/replicationcontrollers/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-replicationcontroller-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ReplicationController. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/replicationcontrollers</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-replicationcontroller-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ReplicationController. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/replicationcontrollers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-replicationcontroller-v1-core">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-replicationcontroller-v1-core">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-replicationcontroller-v1-core">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-replicationcontroller-v1-core">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="misc-operations-replicationcontroller-v1-core">
<H2 class="toc-item operation-category">Misc Operations</H2>
<DIV class="operation-container" id="read-scale-replicationcontroller-v1-core">
<H2 class="toc-item operation">Read Scale</H2>
<P>read scale of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-scale-replicationcontroller-v1-core">
<H2 class="toc-item operation">Replace Scale</H2>
<P>replace scale of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-scale-replicationcontroller-v1-core">
<H2 class="toc-item operation">Patch Scale</H2>
<P>partially update scale of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="statefulset-v1-apps">
<H1 class="toc-item resource"><span class="gvk"><span class="k">StatefulSet</span> <span class="v">v1</span> <span class="g">apps</span></span></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-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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>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>ordinals</CODE><BR /><I><a href="#statefulsetordinals-v1-apps">StatefulSetOrdinals</a></I></TD><TD>ordinals controls the numbering of replica indices in a StatefulSet. The default ordinals behavior assigns a &#34;0&#34; index to the first replica and increments the index by one for each additional replica requested.</TD></TR>
<TR><TD><CODE>persistentVolumeClaimRetentionPolicy</CODE><BR /><I><a href="#statefulsetpersistentvolumeclaimretentionpolicy-v1-apps">StatefulSetPersistentVolumeClaimRetentionPolicy</a></I></TD><TD>persistentVolumeClaimRetentionPolicy describes the lifecycle of persistent volume claims created from volumeClaimTemplates. By default, all persistent volume claims are created as needed and retained until manually deleted. This policy allows the lifecycle to be altered, for example by deleting persistent volume claims when their stateful set is deleted, or when their pod is scaled down.</TD></TR>
<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. Each pod will be named with the format &lt;statefulsetname&gt;-&lt;podindex&gt;. For example, a pod in a StatefulSet named &#34;web&#34; with index number &#34;3&#34; would be named &#34;web-3&#34;. The only allowed template.spec.restartPolicy value is &#34;Always&#34;.</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 class="inline-definition" 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>availableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of available pods (ready for at least minReadySeconds) targeted by this statefulset.</TD></TR>
<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 for this StatefulSet with 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 class="inline-definition" 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#statefulset-v1-apps">StatefulSet</a> array</I></TD><TD>Items is the list of stateful 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/sig-architecture/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&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-statefulset-v1-apps">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-statefulset-v1-apps">
<H2 class="toc-item operation">Create</H2>
<P>create a StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/apps/v1/namespaces/{namespace}/statefulsets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-statefulset-v1-apps">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-statefulset-v1-apps">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-statefulset-v1-apps">
<H2 class="toc-item operation">Delete</H2>
<P>delete a StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-statefulset-v1-apps">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/statefulsets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-statefulset-v1-apps">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-statefulset-v1-apps">
<H2 class="toc-item operation">Read</H2>
<P>read the specified StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-statefulset-v1-apps">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-statefulset-v1-apps">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/statefulsets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-statefulset-v1-apps">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind StatefulSet. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/statefulsets/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-statefulset-v1-apps">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of StatefulSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/statefulsets</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-statefulset-v1-apps">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of StatefulSet. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/statefulsets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-statefulset-v1-apps">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-statefulset-v1-apps">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-statefulset-v1-apps">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-statefulset-v1-apps">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="misc-operations-statefulset-v1-apps">
<H2 class="toc-item operation-category">Misc Operations</H2>
<DIV class="operation-container" id="read-scale-statefulset-v1-apps">
<H2 class="toc-item operation">Read Scale</H2>
<P>read scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-scale-statefulset-v1-apps">
<H2 class="toc-item operation">Replace Scale</H2>
<P>replace scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-scale-statefulset-v1-apps">
<H2 class="toc-item operation">Patch Scale</H2>
<P>partially update scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/scale</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV id="service-apis">
<H1 class="toc-item section resource-category">Service</H1>
<P>Service API resources are responsible for stitching your workloads together into an accessible Loadbalanced Service. By default,
<A href="#workloads-apis">Workloads</A> are only accessible within the cluster, and they must be exposed externally using a either
a *LoadBalancer* or *NodePort* <A href="#service-v1-core">Service</A>. For development, internally accessible
Workloads can be accessed via proxy through the api master using the <code>kubectl proxy</code> command.</P>
<P>Common resource types:</P>
<UL>
<LI><A href="#service-v1-core">Services</A> for providing a single ip endpoint loadbalanced across multiple Workload replicas.</LI>
<LI><A href="#ingress-v1beta1-extensions">Ingress</A> for providing a https(s) endpoint http(s) routed to one or more *Services*.</LI>
</UL>
</DIV>
<DIV class="resource-container" id="endpoints-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Endpoints</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-endpoints-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-endpoints-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create Endpoints</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/endpoints</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-endpoints-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Endpoints</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/endpoints/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-endpoints-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Endpoints</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/endpoints/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-endpoints-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete Endpoints</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/endpoints/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-endpoints-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Endpoints</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/endpoints</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-endpoints-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-endpoints-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Endpoints</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/endpoints/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-endpoints-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Endpoints</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/endpoints</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-endpoints-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Endpoints</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/endpoints</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-endpoints-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Endpoints. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/endpoints/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-endpoints-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Endpoints. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/endpoints</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-endpoints-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Endpoints. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/endpoints</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="endpointslice-v1-discovery-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">EndpointSlice</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointSlice</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="#endpointslicelist-v1-discovery-k8s-io">EndpointSliceList [discovery/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>addressType</CODE><BR /><I>string</I></TD><TD>addressType specifies the type of address carried by this EndpointSlice. All addresses in this slice must be the same type. This field is immutable after creation. The following address types are currently supported: * IPv4: Represents an IPv4 Address. * IPv6: Represents an IPv6 Address. * FQDN: Represents a Fully Qualified Domain Name.</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>endpoints</CODE><BR /><I><a href="#endpoint-v1-discovery-k8s-io">Endpoint</a> array</I></TD><TD>endpoints is a list of unique endpoints in this slice. Each slice may include a maximum of 1000 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/sig-architecture/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>ports</CODE><BR /><I><a href="#endpointport-v1-discovery-k8s-io">EndpointPort</a> array</I></TD><TD>ports specifies the list of network ports exposed by each endpoint in this slice. Each port must have a unique name. When ports is empty, it indicates that there are no defined ports. When a port is defined with a nil port value, it indicates &#34;all ports&#34;. Each slice may include a maximum of 100 ports.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="endpointslicelist-v1-discovery-k8s-io">EndpointSliceList v1 discovery</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a> array</I></TD><TD>items is the list of endpoint slices</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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create an EndpointSlice</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified EndpointSlice</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified EndpointSlice</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete an EndpointSlice</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of EndpointSlice</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified EndpointSlice</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind EndpointSlice</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/discovery.k8s.io/v1/namespaces/{namespace}/endpointslices</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpointslicelist-v1-discovery-k8s-io">EndpointSliceList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind EndpointSlice</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/discovery.k8s.io/v1/endpointslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpointslicelist-v1-discovery-k8s-io">EndpointSliceList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/discovery.k8s.io/v1/watch/namespaces/{namespace}/endpointslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the EndpointSlice</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/discovery.k8s.io/v1/watch/namespaces/{namespace}/endpointslices</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-endpointslice-v1-discovery-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of EndpointSlice. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/discovery.k8s.io/v1/watch/endpointslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="ingress-v1-networking-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Ingress</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>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-v1-networking-k8s-io">IngressList [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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#ingressspec-v1-networking-k8s-io">IngressSpec</a></I></TD><TD>spec is the desired state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#ingressstatus-v1-networking-k8s-io">IngressStatus</a></I></TD><TD>status is the current state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="ingressspec-v1-networking-k8s-io">IngressSpec v1 networking</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingress-v1-networking-k8s-io">Ingress [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>defaultBackend</CODE><BR /><I><a href="#ingressbackend-v1-networking-k8s-io">IngressBackend</a></I></TD><TD>defaultBackend is the backend that should handle requests that don&#39;t match any rule. If Rules are not specified, DefaultBackend must be specified. If DefaultBackend is not set, the handling of requests that do not match any of the rules will be up to the Ingress controller.</TD></TR>
<TR><TD><CODE>ingressClassName</CODE><BR /><I>string</I></TD><TD>ingressClassName is the name of an IngressClass cluster resource. Ingress controller implementations use this field to know whether they should be serving this Ingress resource, by a transitive connection (controller -&gt; IngressClass -&gt; Ingress resource). Although the `kubernetes.io/ingress.class` annotation (simple constant name) was never formally defined, it was widely supported by Ingress controllers to create a direct binding between Ingress controller and Ingress resources. Newly created Ingress resources should prefer using the field. However, even though the annotation is officially deprecated, for backwards compatibility reasons, ingress controllers should still honor that annotation if present.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#ingressrule-v1-networking-k8s-io">IngressRule</a> array</I></TD><TD>rules is 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-v1-networking-k8s-io">IngressTLS</a> array</I></TD><TD>tls represents the 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 class="inline-definition" id="ingressstatus-v1-networking-k8s-io">IngressStatus v1 networking</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingress-v1-networking-k8s-io">Ingress [networking/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="#ingressloadbalancerstatus-v1-networking-k8s-io">IngressLoadBalancerStatus</a></I></TD><TD>loadBalancer contains the current status of the load-balancer.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="ingresslist-v1-networking-k8s-io">IngressList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#ingress-v1-networking-k8s-io">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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create an Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-networking-k8s-io">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-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-networking-k8s-io">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-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete an Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-networking-k8s-io">IngressList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/ingresses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-networking-k8s-io">IngressList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Ingress. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/ingresses/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Ingress. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/ingresses</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Ingress. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/watch/ingresses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-ingress-v1-networking-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified Ingress</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-networking-k8s-io">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-v1-networking-k8s-io">Ingress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingress-v1-networking-k8s-io">Ingress</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="ingressclass-v1-networking-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">IngressClass</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>IngressClass</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="#ingressclasslist-v1-networking-k8s-io">IngressClassList [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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#ingressclassspec-v1-networking-k8s-io">IngressClassSpec</a></I></TD><TD>spec is the desired state of the IngressClass. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="ingressclassspec-v1-networking-k8s-io">IngressClassSpec v1 networking</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressclass-v1-networking-k8s-io">IngressClass [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>controller</CODE><BR /><I>string</I></TD><TD>controller refers to the name of the controller that should handle this class. This allows for different &#34;flavors&#34; that are controlled by the same controller. For example, you may have different parameters for the same implementing controller. This should be specified as a domain-prefixed path no more than 250 characters in length, e.g. &#34;acme.io/ingress-controller&#34;. This field is immutable.</TD></TR>
<TR><TD><CODE>parameters</CODE><BR /><I><a href="#ingressclassparametersreference-v1-networking-k8s-io">IngressClassParametersReference</a></I></TD><TD>parameters is a link to a custom resource containing additional configuration for the controller. This is optional if the controller does not require extra parameters.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="ingressclasslist-v1-networking-k8s-io">IngressClassList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a> array</I></TD><TD>items is the list of IngressClasses.</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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create an IngressClass</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/networking.k8s.io/v1/ingressclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified IngressClass</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/networking.k8s.io/v1/ingressclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified IngressClass</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/networking.k8s.io/v1/ingressclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete an IngressClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1/ingressclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of IngressClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1/ingressclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified IngressClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/ingressclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingressclass-v1-networking-k8s-io">IngressClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind IngressClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/ingressclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingressclasslist-v1-networking-k8s-io">IngressClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind IngressClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/watch/ingressclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IngressClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-ingressclass-v1-networking-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of IngressClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/watch/ingressclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="service-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Service</span> <span class="v">v1</span> <span class="g">core</span></span></H1>
<DIV class="samples-container">
<P>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-target="#example-service-v1-core" aria-controls="example-service-v1-core"
aria-expanded="false">show example</BUTTON>
</P>
<DIV class="collapse" id="example-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="example"><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>
<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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>allocateLoadBalancerNodePorts</CODE><BR /><I>boolean</I></TD><TD>allocateLoadBalancerNodePorts defines if NodePorts will be automatically allocated for services with type LoadBalancer. Default is &#34;true&#34;. It may be set to &#34;false&#34; if the cluster load-balancer does not rely on NodePorts. If the caller requests specific NodePorts (by specifying a value), those requests will be respected, regardless of this field. This field may only be set for services with type LoadBalancer and will be cleared if the type is changed to any other type.</TD></TR>
<TR><TD><CODE>clusterIP</CODE><BR /><I>string</I></TD><TD>clusterIP is the IP address of the service and is usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service; otherwise creation of the service will fail. This field may not be changed through updates unless the type field is also being changed to ExternalName (which requires this field to be blank) or the type field is being changed from ExternalName (in which case this field may optionally be specified, as describe above). Valid values are &#34;None&#34;, empty string (&#34;&#34;), or a valid IP address. Setting this to &#34;None&#34; makes a &#34;headless service&#34; (no virtual IP), which is useful when direct endpoint connections are preferred and proxying is not required. Only applies to types ClusterIP, NodePort, and LoadBalancer. If this field is specified when creating a Service of type ExternalName, creation will fail. This field will be wiped when updating a Service to type ExternalName. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies</TD></TR>
<TR><TD><CODE>clusterIPs</CODE><BR /><I>string array</I></TD><TD>ClusterIPs is a list of IP addresses assigned to this service, and are usually assigned randomly. If an address is specified manually, is in-range (as per system configuration), and is not in use, it will be allocated to the service; otherwise creation of the service will fail. This field may not be changed through updates unless the type field is also being changed to ExternalName (which requires this field to be empty) or the type field is being changed from ExternalName (in which case this field may optionally be specified, as describe above). Valid values are &#34;None&#34;, empty string (&#34;&#34;), or a valid IP address. Setting this to &#34;None&#34; makes a &#34;headless service&#34; (no virtual IP), which is useful when direct endpoint connections are preferred and proxying is not required. Only applies to types ClusterIP, NodePort, and LoadBalancer. If this field is specified when creating a Service of type ExternalName, creation will fail. This field will be wiped when updating a Service to type ExternalName. If this field is not specified, it will be initialized from the clusterIP field. If this field is specified, clients must ensure that clusterIPs[0] and clusterIP have the same value. This field may hold a maximum of two entries (dual-stack IPs, in either order). These IPs must correspond to the values of the ipFamilies field. Both clusterIPs and ipFamilies are governed by the ipFamilyPolicy field. 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 discovery mechanisms will return as an alias for this service (e.g. a DNS CNAME record). No proxying will be involved. Must be a lowercase RFC-1123 hostname (https://tools.ietf.org/html/rfc1123) and requires `type` to be &#34;ExternalName&#34;.</TD></TR>
<TR><TD><CODE>externalTrafficPolicy</CODE><BR /><I>string</I></TD><TD>externalTrafficPolicy describes how nodes distribute service traffic they receive on one of the Service&#39;s &#34;externally-facing&#34; addresses (NodePorts, ExternalIPs, and LoadBalancer IPs). If set to &#34;Local&#34;, the proxy will configure the service in a way that assumes that external load balancers will take care of balancing the service traffic between nodes, and so each node will deliver traffic only to the node-local endpoints of the service, without masquerading the client source IP. (Traffic mistakenly sent to a node with no endpoints will be dropped.) The default value, &#34;Cluster&#34;, uses the standard behavior of routing to all endpoints evenly (possibly modified by topology and other features). Note that traffic sent to an External IP or LoadBalancer IP from within the cluster will always get &#34;Cluster&#34; semantics, but clients sending to a NodePort from within the cluster may need to take traffic policy into account when picking a node.</TD></TR>
<TR><TD><CODE>healthCheckNodePort</CODE><BR /><I>integer</I></TD><TD>healthCheckNodePort specifies the healthcheck nodePort for the service. This only applies when type is set to LoadBalancer and externalTrafficPolicy is set to Local. If a value is specified, is in-range, and is not in use, it will be used. If not specified, a value will be automatically allocated. External systems (e.g. load-balancers) can use this port to determine if a given node holds endpoints for this service or not. If this field is specified when creating a Service which does not need it, creation will fail. This field will be wiped when updating a Service to no longer need it (e.g. changing type). This field cannot be updated once set.</TD></TR>
<TR><TD><CODE>internalTrafficPolicy</CODE><BR /><I>string</I></TD><TD>InternalTrafficPolicy describes how nodes distribute service traffic they receive on the ClusterIP. If set to &#34;Local&#34;, the proxy will assume that pods only want to talk to endpoints of the service on the same node as the pod, dropping the traffic if there are no local endpoints. The default value, &#34;Cluster&#34;, uses the standard behavior of routing to all endpoints evenly (possibly modified by topology and other features).</TD></TR>
<TR><TD><CODE>ipFamilies</CODE><BR /><I>string array</I></TD><TD>IPFamilies is a list of IP families (e.g. IPv4, IPv6) assigned to this service. This field is usually assigned automatically based on cluster configuration and the ipFamilyPolicy field. If this field is specified manually, the requested family is available in the cluster, and ipFamilyPolicy allows it, it will be used; otherwise creation of the service will fail. This field is conditionally mutable: it allows for adding or removing a secondary IP family, but it does not allow changing the primary IP family of the Service. Valid values are &#34;IPv4&#34; and &#34;IPv6&#34;. This field only applies to Services of types ClusterIP, NodePort, and LoadBalancer, and does apply to &#34;headless&#34; services. This field will be wiped when updating a Service to type ExternalName. This field may hold a maximum of two entries (dual-stack families, in either order). These families must correspond to the values of the clusterIPs field, if specified. Both clusterIPs and ipFamilies are governed by the ipFamilyPolicy field.</TD></TR>
<TR><TD><CODE>ipFamilyPolicy</CODE><BR /><I>string</I></TD><TD>IPFamilyPolicy represents the dual-stack-ness requested or required by this Service. If there is no value provided, then this field will be set to SingleStack. Services can be &#34;SingleStack&#34; (a single IP family), &#34;PreferDualStack&#34; (two IP families on dual-stack configured clusters or a single IP family on single-stack clusters), or &#34;RequireDualStack&#34; (two IP families on dual-stack configured clusters, otherwise fail). The ipFamilies and clusterIPs fields depend on the value of this field. This field will be wiped when updating a service to type ExternalName.</TD></TR>
<TR><TD><CODE>loadBalancerClass</CODE><BR /><I>string</I></TD><TD>loadBalancerClass is the class of the load balancer implementation this Service belongs to. If specified, the value of this field must be a label-style identifier, with an optional prefix, e.g. &#34;internal-vip&#34; or &#34;example.com/internal-vip&#34;. Unprefixed names are reserved for end-users. This field can only be set when the Service type is &#39;LoadBalancer&#39;. If not set, the default load balancer implementation is used, today this is typically done through the cloud provider integration, but should apply for any default implementation. If set, it is assumed that a load balancer implementation is watching for Services with a matching class. Any default load balancer implementation (e.g. cloud providers) should ignore Services that set this field. This field can only be set when creating or updating a Service to type &#39;LoadBalancer&#39;. Once set, it can not be changed. This field will be wiped when a service is updated to a non &#39;LoadBalancer&#39; type.</TD></TR>
<TR><TD><CODE>loadBalancerIP</CODE><BR /><I>string</I></TD><TD>Only applies to Service Type: LoadBalancer. 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. Deprecated: This field was under-specified and its meaning varies across implementations. Using it is non-portable and it may not support dual-stack. Users are encouraged to use implementation-specific annotations when available.</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/create-external-load-balancer/</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 indicates that any agent which deals with endpoints for this Service should disregard any indications of ready/not-ready. The primary use case for setting this field is for a StatefulSet&#39;s Headless Service to propagate SRV DNS records for its Pods for the purpose of peer discovery. The Kubernetes controllers that generate Endpoints and EndpointSlice resources for Services interpret this to mean that all endpoints are considered &#34;ready&#34; even if the Pods themselves are not. Agents which consume only Kubernetes generated endpoints through the Endpoints or EndpointSlice resources can safely assume this behavior.</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>trafficDistribution</CODE><BR /><I>string</I></TD><TD>TrafficDistribution offers a way to express preferences for how traffic is distributed to Service endpoints. Implementations can use this field as a hint, but are not required to guarantee strict adherence. If the field is not set, the implementation will apply its default routing strategy. If set to &#34;PreferClose&#34;, implementations should prioritize endpoints that are topologically close (e.g., same zone). This is a beta field and requires enabling ServiceTrafficDistribution feature.</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;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 or EndpointSlice objects. If clusterIP is &#34;None&#34;, no virtual IP is allocated and the endpoints are published as a set of endpoints rather than a virtual IP. &#34;NodePort&#34; builds on ClusterIP and allocates a port on every node which routes to the same endpoints as the clusterIP. &#34;LoadBalancer&#34; builds on NodePort and creates an external load-balancer (if supported in the current cloud) which routes to the same endpoints as the clusterIP. &#34;ExternalName&#34; aliases this service to the specified externalName. Several other fields do not apply to ExternalName services. More info: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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>conditions</CODE><BR /><I><a href="#condition-v1-meta">Condition</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</TD></TR>
<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 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-service-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-service-v1-core">
<H2 class="toc-item operation">Create</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>POST /api/v1/namespaces/{namespace}/services</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-service-v1-core">
<H2 class="toc-item operation">Patch</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/services/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-service-v1-core">
<H2 class="toc-item operation">Replace</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>PUT /api/v1/namespaces/{namespace}/services/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-service-v1-core">
<H2 class="toc-item operation">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/services/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-service-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Service</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/services</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-service-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-service-v1-core">
<H2 class="toc-item operation">Read</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>GET /api/v1/namespaces/{namespace}/services/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-service-v1-core">
<H2 class="toc-item operation">List</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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>
<p><CODE>GET /api/v1/namespaces/{namespace}/services</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-service-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Service</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/services</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-service-v1-core">
<H2 class="toc-item operation">Watch</H2>
<BUTTON class="btn btn-info" type="button" data-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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-bs-toggle="collapse"
data-bs-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. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/services/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-service-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Service. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/services</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-service-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Service. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/services</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-service-v1-core">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-service-v1-core">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified Service</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/services/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-service-v1-core">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified Service</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/services/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-service-v1-core">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified Service</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/services/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="proxy-operations-service-v1-core">
<H2 class="toc-item operation-category">Proxy Operations</H2>
<DIV class="operation-container" id="create-connect-proxy-service-v1-core">
<H2 class="toc-item operation">Create Connect Proxy</H2>
<P>connect POST requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="create-connect-proxy-path-service-v1-core">
<H2 class="toc-item operation">Create Connect Proxy Path</H2>
<P>connect POST requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</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>
</DIV>
<DIV class="operation-container" id="delete-connect-proxy-service-v1-core">
<H2 class="toc-item operation">Delete Connect Proxy</H2>
<P>connect DELETE requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="delete-connect-proxy-path-service-v1-core">
<H2 class="toc-item operation">Delete Connect Proxy Path</H2>
<P>connect DELETE requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</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>
</DIV>
<DIV class="operation-container" id="get-connect-proxy-service-v1-core">
<H2 class="toc-item operation">Get Connect Proxy</H2>
<P>connect GET requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="get-connect-proxy-path-service-v1-core">
<H2 class="toc-item operation">Get Connect Proxy Path</H2>
<P>connect GET requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</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>
</DIV>
<DIV class="operation-container" id="head-connect-proxy-service-v1-core">
<H2 class="toc-item operation">Head Connect Proxy</H2>
<P>connect HEAD requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>HEAD /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="head-connect-proxy-path-service-v1-core">
<H2 class="toc-item operation">Head Connect Proxy Path</H2>
<P>connect HEAD requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>HEAD /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</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>
</DIV>
<DIV class="operation-container" id="replace-connect-proxy-service-v1-core">
<H2 class="toc-item operation">Replace Connect Proxy</H2>
<P>connect PUT requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and 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>
</DIV>
<DIV class="operation-container" id="replace-connect-proxy-path-service-v1-core">
<H2 class="toc-item operation">Replace Connect Proxy Path</H2>
<P>connect PUT requests to proxy of Service</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceProxyOptions</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>
</DIV>
</DIV>
</DIV>
<DIV id="config-and-storage-apis">
<H1 class="toc-item section resource-category">Config &amp; Storage</H1>
<P>Config and Storage resources are responsible for injecting data into your applications and persisting data externally to your container.</P>
<P>Common resource types:</P>
<UL>
<LI><A href="#configmap-v1-core">ConfigMaps</A> for providing text key value pairs injected into the application through environment variables, command line arguments, or files</LI>
<LI><A href="#secret-v1-core">Secrets</A> for providing binary data injected into the application through files</LI>
<LI><A href="#volume-v1-core">Volumes</A> for providing a filesystem external to the Container. Maybe shared across Containers within the same Pod and have a lifetime persisting beyond a Container or Pod.</LI>
</UL>
</DIV>
<DIV class="resource-container" id="configmap-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ConfigMap</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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>immutable</CODE><BR /><I>boolean</I></TD><TD>Immutable, if set to true, ensures that data stored in the ConfigMap cannot be updated (only object metadata can be modified). If not set to true, the field can be modified at any time. Defaulted to nil.</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-configmap-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-configmap-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a ConfigMap</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/configmaps</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-configmap-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ConfigMap</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/configmaps/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-configmap-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ConfigMap</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/configmaps/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-configmap-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ConfigMap</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/configmaps/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-configmap-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ConfigMap</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/configmaps</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-configmap-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-configmap-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ConfigMap</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/configmaps/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-configmap-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ConfigMap</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/configmaps</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-configmap-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ConfigMap</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/configmaps</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-configmap-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ConfigMap. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/configmaps/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-configmap-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ConfigMap. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/configmaps</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-configmap-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ConfigMap. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/configmaps</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="csidriver-v1-storage-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">CSIDriver</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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>CSIDriver</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="#csidriverlist-v1-storage-k8s-io">CSIDriverList [storage/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/sig-architecture/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/sig-architecture/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. metadata.Name indicates the name of the CSI driver that this object refers to; it MUST be the same name returned by the CSI GetPluginName() call for that driver. The driver name must be 63 characters or less, beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), dots (.), and alphanumerics between. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#csidriverspec-v1-storage-k8s-io">CSIDriverSpec</a></I></TD><TD>spec represents the specification of the CSI Driver.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="csidriverspec-v1-storage-k8s-io">CSIDriverSpec v1 storage</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#csidriver-v1-storage-k8s-io">CSIDriver [storage/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>attachRequired</CODE><BR /><I>boolean</I></TD><TD>attachRequired indicates this CSI volume driver requires an attach operation (because it implements the CSI ControllerPublishVolume() method), and that the Kubernetes attach detach controller should call the attach volume interface which checks the volumeattachment status and waits until the volume is attached before proceeding to mounting. The CSI external-attacher coordinates with CSI volume driver and updates the volumeattachment status when the attach operation is complete. If the CSIDriverRegistry feature gate is enabled and the value is specified to false, the attach operation will be skipped. Otherwise the attach operation will be called. This field is immutable.</TD></TR>
<TR><TD><CODE>fsGroupPolicy</CODE><BR /><I>string</I></TD><TD>fsGroupPolicy defines if the underlying volume supports changing ownership and permission of the volume before being mounted. Refer to the specific FSGroupPolicy values for additional details. This field was immutable in Kubernetes &lt; 1.29 and now is mutable. Defaults to ReadWriteOnceWithFSType, which will examine each volume to determine if Kubernetes should modify ownership and permissions of the volume. With the default policy the defined fsGroup will only be applied if a fstype is defined and the volume&#39;s access mode contains ReadWriteOnce.</TD></TR>
<TR><TD><CODE>podInfoOnMount</CODE><BR /><I>boolean</I></TD><TD>podInfoOnMount indicates this CSI volume driver requires additional pod information (like podName, podUID, etc.) during mount operations, if set to true. If set to false, pod information will not be passed on mount. Default is false. The CSI driver specifies podInfoOnMount as part of driver deployment. If true, Kubelet will pass pod information as VolumeContext in the CSI NodePublishVolume() calls. The CSI driver is responsible for parsing and validating the information passed in as VolumeContext. The following VolumeContext will be passed if podInfoOnMount is set to true. This list might grow, but the prefix will be used. &#34;csi.storage.k8s.io/pod.name&#34;: pod.Name &#34;csi.storage.k8s.io/pod.namespace&#34;: pod.Namespace &#34;csi.storage.k8s.io/pod.uid&#34;: string(pod.UID) &#34;csi.storage.k8s.io/ephemeral&#34;: &#34;true&#34; if the volume is an ephemeral inline volume defined by a CSIVolumeSource, otherwise &#34;false&#34; &#34;csi.storage.k8s.io/ephemeral&#34; is a new feature in Kubernetes 1.16. It is only required for drivers which support both the &#34;Persistent&#34; and &#34;Ephemeral&#34; VolumeLifecycleMode. Other drivers can leave pod info disabled and/or ignore this field. As Kubernetes 1.15 doesn&#39;t support this field, drivers can only support one mode when deployed on such a cluster and the deployment determines which mode that is, for example via a command line parameter of the driver. This field was immutable in Kubernetes &lt; 1.29 and now is mutable.</TD></TR>
<TR><TD><CODE>requiresRepublish</CODE><BR /><I>boolean</I></TD><TD>requiresRepublish indicates the CSI driver wants `NodePublishVolume` being periodically called to reflect any possible change in the mounted volume. This field defaults to false. Note: After a successful initial NodePublishVolume call, subsequent calls to NodePublishVolume should only update the contents of the volume. New mount points will not be seen by a running container.</TD></TR>
<TR><TD><CODE>seLinuxMount</CODE><BR /><I>boolean</I></TD><TD>seLinuxMount specifies if the CSI driver supports &#34;-o context&#34; mount option. When &#34;true&#34;, the CSI driver must ensure that all volumes provided by this CSI driver can be mounted separately with different `-o context` options. This is typical for storage backends that provide volumes as filesystems on block devices or as independent shared volumes. Kubernetes will call NodeStage / NodePublish with &#34;-o context=xyz&#34; mount option when mounting a ReadWriteOncePod volume used in Pod that has explicitly set SELinux context. In the future, it may be expanded to other volume AccessModes. In any case, Kubernetes will ensure that the volume is mounted only with a single SELinux context. When &#34;false&#34;, Kubernetes won&#39;t pass any special SELinux mount options to the driver. This is typical for volumes that represent subdirectories of a bigger shared filesystem. Default is &#34;false&#34;.</TD></TR>
<TR><TD><CODE>storageCapacity</CODE><BR /><I>boolean</I></TD><TD>storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information, if set to true. The check can be enabled immediately when deploying a driver. In that case, provisioning new volumes with late binding will pause until the driver deployment has published some suitable CSIStorageCapacity object. Alternatively, the driver can be deployed with the field unset or false and it can be flipped later when storage capacity information has been published. This field was immutable in Kubernetes &lt;= 1.22 and now is mutable.</TD></TR>
<TR><TD><CODE>tokenRequests</CODE><BR /><I><a href="#tokenrequest-v1-storage-k8s-io">TokenRequest</a> array</I></TD><TD>tokenRequests indicates the CSI driver needs pods&#39; service account tokens it is mounting volume for to do necessary authentication. Kubelet will pass the tokens in VolumeContext in the CSI NodePublishVolume calls. The CSI driver should parse and validate the following VolumeContext: &#34;csi.storage.k8s.io/serviceAccount.tokens&#34;: { &#34;&lt;audience&gt;&#34;: { &#34;token&#34;: &lt;token&gt;, &#34;expirationTimestamp&#34;: &lt;expiration timestamp in RFC3339&gt;, }, ... } Note: Audience in each TokenRequest should be different and at most one token is empty string. To receive a new token after expiry, RequiresRepublish can be used to trigger NodePublishVolume periodically.</TD></TR>
<TR><TD><CODE>volumeLifecycleModes</CODE><BR /><I>string array</I></TD><TD>volumeLifecycleModes defines what kind of volumes this CSI volume driver supports. The default if the list is empty is &#34;Persistent&#34;, which is the usage defined by the CSI specification and implemented in Kubernetes via the usual PV/PVC mechanism. The other mode is &#34;Ephemeral&#34;. In this mode, volumes are defined inline inside the pod spec with CSIVolumeSource and their lifecycle is tied to the lifecycle of that pod. A driver has to be aware of this because it is only going to get a NodePublishVolume call for such a volume. For more information about implementing this mode, see https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html A driver can support one or more of these modes and more modes may be added in the future. This field is beta. This field is immutable.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="csidriverlist-v1-storage-k8s-io">CSIDriverList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a> array</I></TD><TD>items is the list of CSIDriver</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a CSIDriver</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/storage.k8s.io/v1/csidrivers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified CSIDriver</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storage.k8s.io/v1/csidrivers/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified CSIDriver</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storage.k8s.io/v1/csidrivers/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a CSIDriver</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/csidrivers/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of CSIDriver</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/csidrivers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified CSIDriver</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/csidrivers/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csidriver-v1-storage-k8s-io">CSIDriver</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind CSIDriver</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/csidrivers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csidriverlist-v1-storage-k8s-io">CSIDriverList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind CSIDriver. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/csidrivers/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIDriver</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-csidriver-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of CSIDriver. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/csidrivers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="csinode-v1-storage-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">CSINode</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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>CSINode</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="#csinodelist-v1-storage-k8s-io">CSINodeList [storage/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/sig-architecture/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/sig-architecture/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. metadata.name must be the Kubernetes node name.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#csinodespec-v1-storage-k8s-io">CSINodeSpec</a></I></TD><TD>spec is the specification of CSINode</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="csinodespec-v1-storage-k8s-io">CSINodeSpec v1 storage</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#csinode-v1-storage-k8s-io">CSINode [storage/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>drivers</CODE><BR /><I><a href="#csinodedriver-v1-storage-k8s-io">CSINodeDriver</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>drivers is a list of information of all CSI Drivers existing on a node. If all drivers in the list are uninstalled, this can become empty.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="csinodelist-v1-storage-k8s-io">CSINodeList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a> array</I></TD><TD>items is the list of CSINode</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a CSINode</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/storage.k8s.io/v1/csinodes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified CSINode</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storage.k8s.io/v1/csinodes/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified CSINode</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storage.k8s.io/v1/csinodes/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a CSINode</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/csinodes/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of CSINode</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/csinodes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified CSINode</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/csinodes/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csinode-v1-storage-k8s-io">CSINode</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind CSINode</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/csinodes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csinodelist-v1-storage-k8s-io">CSINodeList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind CSINode. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/csinodes/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSINode</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-csinode-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of CSINode. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/csinodes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="csistoragecapacity-v1-storage-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">CSIStorageCapacity</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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>CSIStorageCapacity</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="#csistoragecapacitylist-v1-storage-k8s-io">CSIStorageCapacityList [storage/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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>capacity</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>capacity is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields. The semantic is currently (CSI spec 1.2) defined as: The available capacity, in bytes, of the storage that can be used to provision volumes. If not set, that information is currently unavailable.</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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>maximumVolumeSize</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>maximumVolumeSize is the value reported by the CSI driver in its GetCapacityResponse for a GetCapacityRequest with topology and parameters that match the previous fields. This is defined since CSI spec 1.4.0 as the largest size that may be used in a CreateVolumeRequest.capacity_range.required_bytes field to create a volume with the same parameters as those in GetCapacityRequest. The corresponding value in the Kubernetes API is ResourceRequirements.Requests in a volume claim.</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. The name has no particular meaning. It must be a DNS subdomain (dots allowed, 253 characters). To ensure that there are no conflicts with other CSI drivers on the cluster, the recommendation is to use csisc-&lt;uuid&gt;, a generated name, or a reverse-domain name which ends with the unique CSI driver name. Objects are namespaced. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>nodeTopology</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>nodeTopology defines which nodes have access to the storage for which capacity was reported. If not set, the storage is not accessible from any node in the cluster. If empty, the storage is accessible from all nodes. This field is immutable.</TD></TR>
<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>storageClassName represents the name of the StorageClass that the reported capacity applies to. It must meet the same requirements as the name of a StorageClass object (non-empty, DNS subdomain). If that object no longer exists, the CSIStorageCapacity object is obsolete and should be removed by its creator. This field is immutable.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="csistoragecapacitylist-v1-storage-k8s-io">CSIStorageCapacityList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a> array</I></TD><TD>items is the list of CSIStorageCapacity 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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a CSIStorageCapacity</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/storage.k8s.io/v1/namespaces/{namespace}/csistoragecapacities</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified CSIStorageCapacity</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storage.k8s.io/v1/namespaces/{namespace}/csistoragecapacities/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified CSIStorageCapacity</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storage.k8s.io/v1/namespaces/{namespace}/csistoragecapacities/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a CSIStorageCapacity</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/namespaces/{namespace}/csistoragecapacities/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of CSIStorageCapacity</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/namespaces/{namespace}/csistoragecapacities</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified CSIStorageCapacity</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/namespaces/{namespace}/csistoragecapacities/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind CSIStorageCapacity</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/namespaces/{namespace}/csistoragecapacities</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csistoragecapacitylist-v1-storage-k8s-io">CSIStorageCapacityList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind CSIStorageCapacity</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/csistoragecapacities</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#csistoragecapacitylist-v1-storage-k8s-io">CSIStorageCapacityList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/namespaces/{namespace}/csistoragecapacities/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CSIStorageCapacity</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/namespaces/{namespace}/csistoragecapacities</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-csistoragecapacity-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of CSIStorageCapacity. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/csistoragecapacities</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="secret-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Secret</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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>immutable</CODE><BR /><I>boolean</I></TD><TD>Immutable, if set to true, ensures that data stored in the Secret cannot be updated (only object metadata can be modified). If not set to true, the field can be modified at any time. Defaulted to nil.</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/sig-architecture/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/sig-architecture/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 input field for convenience. All keys and values are merged into the data field on write, overwriting any existing values. The stringData field 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. More info: https://kubernetes.io/docs/concepts/configuration/secret/#secret-types</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-secret-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-secret-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a Secret</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/secrets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-secret-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Secret</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/secrets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-secret-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Secret</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/secrets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-secret-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a Secret</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/secrets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-secret-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Secret</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/secrets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-secret-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-secret-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Secret</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/secrets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-secret-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Secret</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/secrets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-secret-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Secret</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/secrets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-secret-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Secret. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/secrets/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-secret-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Secret. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/secrets</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-secret-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Secret. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/secrets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="persistentvolumeclaim-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">PersistentVolumeClaim</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</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/sig-architecture/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/sig-architecture/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/sig-architecture/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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>
<LI><a href="#persistentvolumeclaimtemplate-v1-core">PersistentVolumeClaimTemplate [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>dataSource</CODE><BR /><I><a href="#typedlocalobjectreference-v1-core">TypedLocalObjectReference</a></I></TD><TD>dataSource field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. When the AnyVolumeDataSource feature gate is enabled, dataSource contents will be copied to dataSourceRef, and dataSourceRef contents will be copied to dataSource when dataSourceRef.namespace is not specified. If the namespace is specified, then dataSourceRef will not be copied to dataSource.</TD></TR>
<TR><TD><CODE>dataSourceRef</CODE><BR /><I><a href="#typedobjectreference-v1-core">TypedObjectReference</a></I></TD><TD>dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn&#39;t specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn&#39;t set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef allows any non-core object, as well as PersistentVolumeClaim objects. * While dataSource ignores disallowed values (dropping them), dataSourceRef preserves all values, and generates an error if a disallowed value is specified. * While dataSource only allows local objects, dataSourceRef allows objects in any namespaces. (Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I><a href="#volumeresourcerequirements-v1-core">VolumeResourceRequirements</a></I></TD><TD>resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. 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>selector is a label query over volumes to consider for binding.</TD></TR>
<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>storageClassName is the 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>volumeAttributesClassName</CODE><BR /><I>string</I></TD><TD>volumeAttributesClassName may be used to set the VolumeAttributesClass used by this claim. If specified, the CSI driver will create or update the volume with the attributes defined in the corresponding VolumeAttributesClass. This has a different purpose than storageClassName, it can be changed after the claim is created. An empty string value means that no VolumeAttributesClass will be applied to the claim but it&#39;s not allowed to reset this field to empty string once it is set. If unspecified and the PersistentVolumeClaim is unbound, the default VolumeAttributesClass will be set by the persistentvolume controller if it exists. If the resource referred to by volumeAttributesClass does not exist, this PersistentVolumeClaim will be set to a Pending state, as reflected by the modifyVolumeStatus field, until such as a resource exists. More info: https://kubernetes.io/docs/concepts/storage/volume-attributes-classes/ (Beta) Using this field requires the VolumeAttributesClass feature gate to be enabled (off by default).</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.</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 class="inline-definition" 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>allocatedResourceStatuses</CODE><BR /><I>object</I></TD><TD>allocatedResourceStatuses stores status of resource being resized for the given PVC. Key names follow standard Kubernetes label syntax. Valid values are either: * Un-prefixed keys: - storage - the capacity of the volume. * Custom resources must use implementation-defined prefixed names such as &#34;example.com/my-custom-resource&#34; Apart from above values - keys that are unprefixed or have kubernetes.io prefix are considered reserved and hence may not be used. ClaimResourceStatus can be in any of following states: - ControllerResizeInProgress: State set when resize controller starts resizing the volume in control-plane. - ControllerResizeFailed: State set when resize has failed in resize controller with a terminal error. - NodeResizePending: State set when resize controller has finished resizing the volume but further resizing of volume is needed on the node. - NodeResizeInProgress: State set when kubelet starts resizing the volume. - NodeResizeFailed: State set when resizing has failed in kubelet with a terminal error. Transient errors don&#39;t set NodeResizeFailed. For example: if expanding a PVC for more capacity - this field can be one of the following states: - pvc.status.allocatedResourceStatus[&#39;storage&#39;] = &#34;ControllerResizeInProgress&#34; - pvc.status.allocatedResourceStatus[&#39;storage&#39;] = &#34;ControllerResizeFailed&#34; - pvc.status.allocatedResourceStatus[&#39;storage&#39;] = &#34;NodeResizePending&#34; - pvc.status.allocatedResourceStatus[&#39;storage&#39;] = &#34;NodeResizeInProgress&#34; - pvc.status.allocatedResourceStatus[&#39;storage&#39;] = &#34;NodeResizeFailed&#34; When this field is not set, it means that no resize operation is in progress for the given PVC. A controller that receives PVC update with previously unknown resourceName or ClaimResourceStatus should ignore the update for the purpose it was designed. For example - a controller that only is responsible for resizing capacity of the volume, should ignore PVC updates that change other valid resources associated with PVC. This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.</TD></TR>
<TR><TD><CODE>allocatedResources</CODE><BR /><I>object</I></TD><TD>allocatedResources tracks the resources allocated to a PVC including its capacity. Key names follow standard Kubernetes label syntax. Valid values are either: * Un-prefixed keys: - storage - the capacity of the volume. * Custom resources must use implementation-defined prefixed names such as &#34;example.com/my-custom-resource&#34; Apart from above values - keys that are unprefixed or have kubernetes.io prefix are considered reserved and hence may not be used. Capacity reported here may be larger than the actual capacity when a volume expansion operation is requested. For storage quota, the larger value from allocatedResources and PVC.spec.resources is used. If allocatedResources is not set, PVC.spec.resources alone is used for quota calculation. If a volume expansion capacity request is lowered, allocatedResources is only lowered if there are no expansion operations in progress and if the actual volume capacity is equal or lower than the requested capacity. A controller that receives PVC update with previously unknown resourceName should ignore the update for the purpose it was designed. For example - a controller that only is responsible for resizing capacity of the volume, should ignore PVC updates that change other valid resources associated with PVC. This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.</TD></TR>
<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>capacity 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>conditions is the current Condition of persistent volume claim. If underlying persistent volume is being resized then the Condition will be set to &#39;Resizing&#39;.</TD></TR>
<TR><TD><CODE>currentVolumeAttributesClassName</CODE><BR /><I>string</I></TD><TD>currentVolumeAttributesClassName is the current name of the VolumeAttributesClass the PVC is using. When unset, there is no VolumeAttributeClass applied to this PersistentVolumeClaim This is a beta field and requires enabling VolumeAttributesClass feature (off by default).</TD></TR>
<TR><TD><CODE>modifyVolumeStatus</CODE><BR /><I><a href="#modifyvolumestatus-v1-core">ModifyVolumeStatus</a></I></TD><TD>ModifyVolumeStatus represents the status object of ControllerModifyVolume operation. When this is unset, there is no ModifyVolume operation being attempted. This is a beta field and requires enabling VolumeAttributesClass feature (off by default).</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 class="inline-definition" 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a> array</I></TD><TD>items is 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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/persistentvolumeclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/persistentvolumeclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/persistentvolumeclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/persistentvolumeclaims</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind PersistentVolumeClaim. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of PersistentVolumeClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/persistentvolumeclaims</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of PersistentVolumeClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/persistentvolumeclaims</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-persistentvolumeclaim-v1-core">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="storageclass-v1-storage-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">StorageClass</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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-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>allowedTopologies 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 only honored by servers that enable the VolumeScheduling 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>mountOptions</CODE><BR /><I>string array</I></TD><TD>mountOptions controls the mountOptions for dynamically provisioned PersistentVolumes of this storage class. 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>reclaimPolicy controls the reclaimPolicy for dynamically provisioned PersistentVolumes of this storage class. 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 only honored by servers that enable the VolumeScheduling feature.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a StorageClass</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/storage.k8s.io/v1/storageclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified StorageClass</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storage.k8s.io/v1/storageclasses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified StorageClass</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storage.k8s.io/v1/storageclasses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a StorageClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/storageclasses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of StorageClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/storageclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified StorageClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/storageclasses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind StorageClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/storageclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind StorageClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/storageclasses/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-storageclass-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of StorageClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/storageclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">StorageVersionMigration</span> <span class="v">v1alpha1</span> <span class="g">storagemigration.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storagemigration.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>StorageVersionMigration</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="#storageversionmigrationlist-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationList [storagemigration/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#storageversionmigrationspec-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationSpec</a></I></TD><TD>Specification of the migration.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#storageversionmigrationstatus-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationStatus</a></I></TD><TD>Status of the migration.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="storageversionmigrationspec-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationSpec v1alpha1 storagemigration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration [storagemigration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continueToken</CODE><BR /><I>string</I></TD><TD>The token used in the list options to get the next chunk of objects to migrate. When the .status.conditions indicates the migration is &#34;Running&#34;, users can use this token to check the progress of the migration.</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I><a href="#groupversionresource-v1alpha1-storagemigration-k8s-io">GroupVersionResource</a></I></TD><TD>The resource that is being migrated. The migrator sends requests to the endpoint serving the resource. Immutable.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="storageversionmigrationstatus-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationStatus v1alpha1 storagemigration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration [storagemigration/v1alpha1]</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="#migrationcondition-v1alpha1-storagemigration-k8s-io">MigrationCondition</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 the migration&#39;s current state.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>ResourceVersion to compare with the GC cache for performing the migration. This is the current resource version of given group, version and resource when kube-controller-manager first observes this StorageVersionMigration resource.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="storageversionmigrationlist-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationList v1alpha1 storagemigration</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Items is the list of StorageVersionMigration</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigrationlist-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind StorageVersionMigration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/watch/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of StorageVersionMigration. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/watch/storageversionmigrations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="volume-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Volume</span> <span class="v">v1</span> <span class="g">core</span></span></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="#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. Deprecated: AWSElasticBlockStore is deprecated. All operations for the in-tree awsElasticBlockStore type are redirected to the ebs.csi.aws.com CSI driver. 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. Deprecated: AzureDisk is deprecated. All operations for the in-tree azureDisk type are redirected to the disk.csi.azure.com CSI driver.</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. Deprecated: AzureFile is deprecated. All operations for the in-tree azureFile type are redirected to the file.csi.azure.com CSI driver.</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. Deprecated: CephFS is deprecated and the in-tree cephfs type is no longer supported.</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. Deprecated: Cinder is deprecated. All operations for the in-tree cinder type are redirected to the cinder.csi.openstack.org CSI driver. More info: https://examples.k8s.io/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>csi</CODE><BR /><I><a href="#csivolumesource-v1-core">CSIVolumeSource</a></I></TD><TD>csi (Container Storage Interface) represents ephemeral storage that is handled by certain external CSI drivers.</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>ephemeral</CODE><BR /><I><a href="#ephemeralvolumesource-v1-core">EphemeralVolumeSource</a></I></TD><TD>ephemeral represents a volume that is handled by a cluster storage driver. The volume&#39;s lifecycle is tied to the pod that defines it - it will be created before the pod starts, and deleted when the pod is removed. Use this if: a) the volume is only needed while the pod runs, b) features of normal volumes like restoring from snapshot or capacity tracking are needed, c) the storage driver is specified through a storage class, and d) the storage driver supports dynamic volume provisioning through a PersistentVolumeClaim (see EphemeralVolumeSource for more information on the connection between this volume type and PersistentVolumeClaim). Use PersistentVolumeClaim or one of the vendor-specific APIs for volumes that persist for longer than the lifecycle of an individual pod. Use CSI for light-weight local ephemeral volumes if the CSI driver is meant to be used that way - see the documentation of the driver for more information. A pod can use both types of ephemeral volumes and persistent volumes at the same time.</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. Deprecated: FlexVolume is deprecated. Consider using a CSIDriver instead.</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. Deprecated: Flocker is deprecated and the in-tree flocker type is no longer supported.</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. Deprecated: GCEPersistentDisk is deprecated. All operations for the in-tree gcePersistentDisk type are redirected to the pd.csi.storage.gke.io CSI driver. 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. Deprecated: Glusterfs is deprecated and the in-tree glusterfs type is no longer supported. More info: https://examples.k8s.io/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>image</CODE><BR /><I><a href="#imagevolumesource-v1-core">ImageVolumeSource</a></I></TD><TD>image represents an OCI object (a container image or artifact) pulled and mounted on the kubelet&#39;s host machine. The volume is resolved at pod startup depending on which PullPolicy value is provided: - Always: the kubelet always attempts to pull the reference. Container creation will fail If the pull fails. - Never: the kubelet never pulls the reference and only uses a local image or artifact. Container creation will fail if the reference isn&#39;t present. - IfNotPresent: the kubelet pulls if the reference isn&#39;t already present on disk. Container creation will fail if the reference isn&#39;t present and the pull fails. The volume gets re-resolved if the pod gets deleted and recreated, which means that new remote content will become available on pod recreation. A failure to resolve or pull the image during pod startup will block containers from starting and may add significant latency. Failures will be retried using normal volume backoff and will be reported on the pod reason and message. The types of objects that may be mounted by this volume are defined by the container runtime implementation on a host machine and at minimum must include all valid types supported by the container image field. The OCI object gets mounted in a single directory (spec.containers[*].volumeMounts.mountPath) by merging the manifest layers in the same way as for container images. The volume will be mounted read-only (ro) and non-executable files (noexec). Sub path mounts for containers are not supported (spec.containers[*].volumeMounts.subpath). The field spec.securityContext.fsGroupChangePolicy has no effect on this volume type.</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://examples.k8s.io/volumes/iscsi/README.md</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name of the volume. 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. Deprecated: PhotonPersistentDisk is deprecated and the in-tree photonPersistentDisk type is no longer supported.</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. Deprecated: PortworxVolume is deprecated. All operations for the in-tree portworxVolume type are redirected to the pxd.portworx.com CSI driver when the CSIMigrationPortworx feature-gate is on.</TD></TR>
<TR><TD><CODE>projected</CODE><BR /><I><a href="#projectedvolumesource-v1-core">ProjectedVolumeSource</a></I></TD><TD>projected 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. Deprecated: Quobyte is deprecated and the in-tree quobyte type is no longer supported.</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. Deprecated: RBD is deprecated and the in-tree rbd type is no longer supported. More info: https://examples.k8s.io/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. Deprecated: ScaleIO is deprecated and the in-tree scaleIO type is no longer supported.</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. Deprecated: StorageOS is deprecated and the in-tree storageos type is no longer supported.</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. Deprecated: VsphereVolume is deprecated. All operations for the in-tree vsphereVolume type are redirected to the csi.vsphere.vmware.com CSI driver.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="volumeattachment-v1-storage-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">VolumeAttachment</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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>VolumeAttachment</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="#volumeattachmentlist-v1-storage-k8s-io">VolumeAttachmentList [storage/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#volumeattachmentspec-v1-storage-k8s-io">VolumeAttachmentSpec</a></I></TD><TD>spec represents 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-v1-storage-k8s-io">VolumeAttachmentStatus</a></I></TD><TD>status represents status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="volumeattachmentspec-v1-storage-k8s-io">VolumeAttachmentSpec v1 storage</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment [storage/v1]</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>nodeName represents the node that the volume should be attached to.</TD></TR>
<TR><TD><CODE>source</CODE><BR /><I><a href="#volumeattachmentsource-v1-storage-k8s-io">VolumeAttachmentSource</a></I></TD><TD>source represents the volume that should be attached.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="volumeattachmentstatus-v1-storage-k8s-io">VolumeAttachmentStatus v1 storage</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment [storage/v1]</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-v1-storage-k8s-io">VolumeError</a></I></TD><TD>attachError represents 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>attached 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>attachmentMetadata is populated with any information returned by the attach operation, upon successful attach, 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-v1-storage-k8s-io">VolumeError</a></I></TD><TD>detachError represents 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 class="inline-definition" id="volumeattachmentlist-v1-storage-k8s-io">VolumeAttachmentList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#volumeattachment-v1-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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/storage.k8s.io/v1/volumeattachments</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storage.k8s.io/v1/volumeattachments/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storage.k8s.io/v1/volumeattachments/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/volumeattachments/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1/volumeattachments</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/volumeattachments/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/volumeattachments</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-storage-k8s-io">VolumeAttachmentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind VolumeAttachment. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/volumeattachments/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of VolumeAttachment. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/watch/volumeattachments</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storage.k8s.io/v1/volumeattachments/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1/volumeattachments/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-volumeattachment-v1-storage-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storage.k8s.io/v1/volumeattachments/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="volumeattributesclass-v1beta1-storage-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">VolumeAttributesClass</span> <span class="v">v1beta1</span> <span class="g">storage.k8s.io</span></span></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>VolumeAttributesClass</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="#volumeattributesclass-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="#volumeattributesclasslist-v1beta1-storage-k8s-io">VolumeAttributesClassList [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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>driverName</CODE><BR /><I>string</I></TD><TD>Name of the CSI driver This field is immutable.</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>parameters</CODE><BR /><I>object</I></TD><TD>parameters hold volume attributes defined by the CSI driver. These values are opaque to the Kubernetes and are passed directly to the CSI driver. The underlying storage provider supports changing these attributes on an existing volume, however the parameters field itself is immutable. To invoke a volume update, a new VolumeAttributesClass should be created with new parameters, and the PersistentVolumeClaim should be updated to reference the new VolumeAttributesClass. This field is required and must contain at least one key/value pair. The keys cannot be empty, and the maximum number of parameters is 512, with a cumulative max size of 256K. If the CSI driver rejects invalid parameters, the target PersistentVolumeClaim will be set to an &#34;Infeasible&#34; state in the modifyVolumeStatus field.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="volumeattributesclasslist-v1beta1-storage-k8s-io">VolumeAttributesClassList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a> array</I></TD><TD>items is the list of VolumeAttributesClass 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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/storage.k8s.io/v1beta1/volumeattributesclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storage.k8s.io/v1beta1/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storage.k8s.io/v1beta1/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1beta1/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1beta1/volumeattributesclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1beta1/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1beta1/volumeattributesclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattributesclasslist-v1beta1-storage-k8s-io">VolumeAttributesClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind VolumeAttributesClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1beta1/watch/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-volumeattributesclass-v1beta1-storage-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of VolumeAttributesClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1beta1/watch/volumeattributesclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV id="metadata-apis">
<H1 class="toc-item section resource-category">Metadata</H1>
<P>Metadata resources are responsible for configuring behavior of your other Resources within the Cluster.</P>
<P>Common resource types:</P>
<UL>
<LI><A href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</A> (HPA) for automatically scaling the replicacount of your workloads in response to load.</LI>
<LI><A href="#poddisruptionbudget-v1alpha1">PodDisruptionBudget</A> for configuring how many replicas in a given workload maybe made concurrently unavailable when performing maintenance.</LI>
<LI><A href="#event-v1-core">Event</A> for notification of resource lifecycle events in the cluster.</LI>
</UL>
</DIV>
<DIV class="resource-container" id="clustertrustbundle-v1alpha1-certificates-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ClusterTrustBundle</span> <span class="v">v1alpha1</span> <span class="g">certificates.k8s.io</span></span></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>v1alpha1</CODE></TD><TD><CODE>ClusterTrustBundle</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="#clustertrustbundlelist-v1alpha1-certificates-k8s-io">ClusterTrustBundleList [certificates/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/sig-architecture/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/sig-architecture/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 contains the object metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#clustertrustbundlespec-v1alpha1-certificates-k8s-io">ClusterTrustBundleSpec</a></I></TD><TD>spec contains the signer (if any) and trust anchors.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="clustertrustbundlespec-v1alpha1-certificates-k8s-io">ClusterTrustBundleSpec v1alpha1 certificates</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle [certificates/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>signerName</CODE><BR /><I>string</I></TD><TD>signerName indicates the associated signer, if any. In order to create or update a ClusterTrustBundle that sets signerName, you must have the following cluster-scoped permission: group=certificates.k8s.io resource=signers resourceName=&lt;the signer name&gt; verb=attest. If signerName is not empty, then the ClusterTrustBundle object must be named with the signer name as a prefix (translating slashes to colons). For example, for the signer name `example.com/foo`, valid ClusterTrustBundle object names include `example.com:foo:abc` and `example.com:foo:v1`. If signerName is empty, then the ClusterTrustBundle object&#39;s name must not have such a prefix. List/watch requests for ClusterTrustBundles can filter on this field using a `spec.signerName=NAME` field selector.</TD></TR>
<TR><TD><CODE>trustBundle</CODE><BR /><I>string</I></TD><TD>trustBundle contains the individual X.509 trust anchors for this bundle, as PEM bundle of PEM-wrapped, DER-formatted X.509 certificates. The data must consist only of PEM certificate blocks that parse as valid X.509 certificates. Each certificate must include a basic constraints extension with the CA bit set. The API server will reject objects that contain duplicate certificates, or that use PEM block headers. Users of ClusterTrustBundles, including Kubelet, are free to reorder and deduplicate certificate blocks in this file according to their own logic, as well as to drop PEM block headers and inter-block data.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="clustertrustbundlelist-v1alpha1-certificates-k8s-io">ClusterTrustBundleList v1alpha1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a> array</I></TD><TD>items is a collection of ClusterTrustBundle 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/sig-architecture/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 contains the list metadata.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ClusterTrustBundle</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/certificates.k8s.io/v1alpha1/clustertrustbundles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ClusterTrustBundle</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ClusterTrustBundle</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ClusterTrustBundle</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ClusterTrustBundle</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/certificates.k8s.io/v1alpha1/clustertrustbundles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ClusterTrustBundle</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/certificates.k8s.io/v1alpha1/clustertrustbundles/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ClusterTrustBundle</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/certificates.k8s.io/v1alpha1/clustertrustbundles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clustertrustbundlelist-v1alpha1-certificates-k8s-io">ClusterTrustBundleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ClusterTrustBundle. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/certificates.k8s.io/v1alpha1/watch/clustertrustbundles/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterTrustBundle</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-clustertrustbundle-v1alpha1-certificates-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ClusterTrustBundle. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/certificates.k8s.io/v1alpha1/watch/clustertrustbundles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="controllerrevision-v1-apps">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ControllerRevision</span> <span class="v">v1</span> <span class="g">apps</span></span></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-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/sig-architecture/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/sig-architecture/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/sig-architecture/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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-controllerrevision-v1-apps">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-controllerrevision-v1-apps">
<H2 class="toc-item operation">Create</H2>
<P>create a ControllerRevision</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/apps/v1/namespaces/{namespace}/controllerrevisions</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-controllerrevision-v1-apps">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-controllerrevision-v1-apps">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-controllerrevision-v1-apps">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ControllerRevision</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-controllerrevision-v1-apps">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ControllerRevision</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apps/v1/namespaces/{namespace}/controllerrevisions</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-controllerrevision-v1-apps">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-controllerrevision-v1-apps">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-controllerrevision-v1-apps">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/namespaces/{namespace}/controllerrevisions</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-controllerrevision-v1-apps">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/controllerrevisions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-controllerrevision-v1-apps">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ControllerRevision. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/controllerrevisions/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-controllerrevision-v1-apps">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ControllerRevision. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/controllerrevisions</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-controllerrevision-v1-apps">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ControllerRevision. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apps/v1/watch/controllerrevisions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="customresourcedefinition-v1-apiextensions-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">CustomResourceDefinition</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">CustomResourceDefinitionList [apiextensions/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#customresourcedefinitionspec-v1-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-v1-apiextensions-k8s-io">CustomResourceDefinitionStatus</a></I></TD><TD>status indicates the actual state of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="customresourcedefinitionspec-v1-apiextensions-k8s-io">CustomResourceDefinitionSpec v1 apiextensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition [apiextensions/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>conversion</CODE><BR /><I><a href="#customresourceconversion-v1-apiextensions-k8s-io">CustomResourceConversion</a></I></TD><TD>conversion defines conversion settings for the CRD.</TD></TR>
<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>group is the API group of the defined custom resource. The custom resources are served under `/apis/&lt;group&gt;/...`. Must match the name of the CustomResourceDefinition (in the form `&lt;names.plural&gt;.&lt;group&gt;`).</TD></TR>
<TR><TD><CODE>names</CODE><BR /><I><a href="#customresourcedefinitionnames-v1-apiextensions-k8s-io">CustomResourceDefinitionNames</a></I></TD><TD>names specify the resource and kind names for the custom resource.</TD></TR>
<TR><TD><CODE>preserveUnknownFields</CODE><BR /><I>boolean</I></TD><TD>preserveUnknownFields indicates that object fields which are not specified in the OpenAPI schema should be preserved when persisting to storage. apiVersion, kind, metadata and known fields inside metadata are always preserved. This field is deprecated in favor of setting `x-preserve-unknown-fields` to true in `spec.versions[*].schema.openAPIV3Schema`. See https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#field-pruning for details.</TD></TR>
<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>scope indicates whether the defined custom resource is cluster- or namespace-scoped. Allowed values are `Cluster` and `Namespaced`.</TD></TR>
<TR><TD><CODE>versions</CODE><BR /><I><a href="#customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion</a> array</I></TD><TD>versions is the list of all API versions of the defined custom resource. Version names are used to compute the order in which served versions are listed in API discovery. 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 class="inline-definition" id="customresourcedefinitionstatus-v1-apiextensions-k8s-io">CustomResourceDefinitionStatus v1 apiextensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition [apiextensions/v1]</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-v1-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-v1-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 lists 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 a migration controller can finish a migration to another version (ensuring no old objects are left in storage), and then remove the rest of the versions from this list. Versions may not be removed from `spec.versions` while they exist in this list.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="customresourcedefinitionlist-v1-apiextensions-k8s-io">CustomResourceDefinitionList v1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a> array</I></TD><TD>items list individual CustomResourceDefinition 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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/apiextensions.k8s.io/v1/customresourcedefinitions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apiextensions.k8s.io/v1/customresourcedefinitions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiextensions.k8s.io/v1/customresourcedefinitions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-apiextensions-k8s-io">CustomResourceDefinitionList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind CustomResourceDefinition. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiextensions.k8s.io/v1/watch/customresourcedefinitions/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of CustomResourceDefinition. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiextensions.k8s.io/v1/watch/customresourcedefinitions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-customresourcedefinition-v1-apiextensions-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apiextensions.k8s.io/v1/customresourcedefinitions/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="deviceclass-v1beta1-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceClass</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceClass</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="#deviceclass-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceclasslist-v1beta1-resource-k8s-io">DeviceClassList [resource/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/sig-architecture/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/sig-architecture/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="#deviceclassspec-v1beta1-resource-k8s-io">DeviceClassSpec</a></I></TD><TD>Spec defines what can be allocated and how to configure it. This is mutable. Consumers have to be prepared for classes changing at any time, either because they get updated or replaced. Claim allocations are done once based on whatever was set in classes at the time of allocation. Changing the spec automatically increments the metadata.generation number.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="deviceclassspec-v1beta1-resource-k8s-io">DeviceClassSpec v1beta1 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>config</CODE><BR /><I><a href="#deviceclassconfiguration-v1beta1-resource-k8s-io">DeviceClassConfiguration</a> array</I></TD><TD>Config defines configuration parameters that apply to each device that is claimed via this class. Some classses may potentially be satisfied by multiple drivers, so each instance of a vendor configuration applies to exactly one driver. They are passed to the driver, but are not considered while allocating the claim.</TD></TR>
<TR><TD><CODE>selectors</CODE><BR /><I><a href="#deviceselector-v1beta1-resource-k8s-io">DeviceSelector</a> array</I></TD><TD>Each selector must be satisfied by a device which is claimed via this class.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="deviceclasslist-v1beta1-resource-k8s-io">DeviceClassList v1beta1 resource</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a> array</I></TD><TD>Items is the list of resource classes.</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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/resource.k8s.io/v1beta1/deviceclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1beta1/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1beta1/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/deviceclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/deviceclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deviceclasslist-v1beta1-resource-k8s-io">DeviceClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind DeviceClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-deviceclass-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of DeviceClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/deviceclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="event-v1-events-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Event</span> <span class="v">v1</span> <span class="g">events.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>Event</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="#eventlist-v1-events-k8s-io">EventList [events/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>action is what action was taken/failed regarding to the regarding object. It is machine-readable. This field cannot be empty for new Events and it can have at most 128 characters.</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>deprecatedCount</CODE><BR /><I>integer</I></TD><TD>deprecatedCount is the 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>deprecatedFirstTimestamp is the 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>deprecatedLastTimestamp is the 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>deprecatedSource is the 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>eventTime is the time when this Event was first observed. It is required.</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>note</CODE><BR /><I>string</I></TD><TD>note is 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>reason is why the action was taken. It is human-readable. This field cannot be empty for new Events and it can have at most 128 characters.</TD></TR>
<TR><TD><CODE>regarding</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>regarding contains 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>related is the 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>reportingController is the name of the controller that emitted this Event, e.g. `kubernetes.io/kubelet`. This field cannot be empty for new Events.</TD></TR>
<TR><TD><CODE>reportingInstance</CODE><BR /><I>string</I></TD><TD>reportingInstance is the ID of the controller instance, e.g. `kubelet-xyzf`. This field cannot be empty for new Events and it can have at most 128 characters.</TD></TR>
<TR><TD><CODE>series</CODE><BR /><I><a href="#eventseries-v1-events-k8s-io">EventSeries</a></I></TD><TD>series is 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 is the type of this event (Normal, Warning), new types could be added in the future. It is machine-readable. This field cannot be empty for new Events.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="eventlist-v1-events-k8s-io">EventList v1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#event-v1-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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-event-v1-events-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-event-v1-events-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create an Event</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/events.k8s.io/v1/namespaces/{namespace}/events</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-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-v1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-event-v1-events-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Event</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/events.k8s.io/v1/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-event-v1-events-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Event</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/events.k8s.io/v1/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-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-v1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#event-v1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-event-v1-events-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete an Event</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/events.k8s.io/v1/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-event-v1-events-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Event</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/events.k8s.io/v1/namespaces/{namespace}/events</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-event-v1-events-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-event-v1-events-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Event</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/events.k8s.io/v1/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-event-v1-events-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Event</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/events.k8s.io/v1/namespaces/{namespace}/events</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-events-k8s-io">EventList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-event-v1-events-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Event</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/events.k8s.io/v1/events</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-events-k8s-io">EventList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-event-v1-events-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Event. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/events.k8s.io/v1/watch/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-event-v1-events-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/events.k8s.io/v1/watch/namespaces/{namespace}/events</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-event-v1-events-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/events.k8s.io/v1/watch/events</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="limitrange-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">LimitRange</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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 class="inline-definition" 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/sig-architecture/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-resources-containers/</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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-limitrange-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-limitrange-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a LimitRange</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/limitranges</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-limitrange-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified LimitRange</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/limitranges/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-limitrange-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified LimitRange</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/limitranges/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-limitrange-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a LimitRange</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/limitranges/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-limitrange-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of LimitRange</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/limitranges</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-limitrange-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-limitrange-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified LimitRange</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/limitranges/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-limitrange-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind LimitRange</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/limitranges</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-limitrange-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind LimitRange</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/limitranges</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-limitrange-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind LimitRange. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/limitranges/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-limitrange-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of LimitRange. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/limitranges</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-limitrange-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of LimitRange. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/limitranges</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="horizontalpodautoscaler-v2-autoscaling">
<H1 class="toc-item resource"><span class="gvk"><span class="k">HorizontalPodAutoscaler</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2]</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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#horizontalpodautoscalerspec-v2-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/sig-architecture/api-conventions.md#spec-and-status.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#horizontalpodautoscalerstatus-v2-autoscaling">HorizontalPodAutoscalerStatus</a></I></TD><TD>status is the current information about the autoscaler.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="horizontalpodautoscalerspec-v2-autoscaling">HorizontalPodAutoscalerSpec v2 autoscaling</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>behavior</CODE><BR /><I><a href="#horizontalpodautoscalerbehavior-v2-autoscaling">HorizontalPodAutoscalerBehavior</a></I></TD><TD>behavior configures the scaling behavior of the target in both Up and Down directions (scaleUp and scaleDown fields respectively). If not set, the default HPAScalingRules for scale up and scale down are used.</TD></TR>
<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-v2-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. If not set, the default metric will be set to 80% average CPU utilization.</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. minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured. Scaling is active as long as at least one metric value is available.</TD></TR>
<TR><TD><CODE>scaleTargetRef</CODE><BR /><I><a href="#crossversionobjectreference-v2-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 class="inline-definition" id="horizontalpodautoscalerstatus-v2-autoscaling">HorizontalPodAutoscalerStatus v2 autoscaling</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler [autoscaling/v2]</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-v2-autoscaling">HorizontalPodAutoscalerCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</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-v2-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 class="inline-definition" id="horizontalpodautoscalerlist-v2-autoscaling">HorizontalPodAutoscalerList v2 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#horizontalpodautoscaler-v2-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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Create</H2>
<P>create a HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v2-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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v2-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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Delete</H2>
<P>delete a HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Read</H2>
<P>read the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v2-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v2/horizontalpodautoscalers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v2-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v2/watch/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v2/watch/namespaces/{namespace}/horizontalpodautoscalers</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v2/watch/horizontalpodautoscalers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-horizontalpodautoscaler-v2-autoscaling">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v2-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-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">MutatingWebhookConfiguration</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</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-v1-admissionregistration-k8s-io">MutatingWebhookConfigurationList [admissionregistration/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>webhooks</CODE><BR /><I><a href="#mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="mutatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">MutatingWebhookConfigurationList v1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#mutatingwebhookconfiguration-v1-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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/mutatingwebhookconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-admissionregistration-k8s-io">MutatingWebhookConfigurationList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind MutatingWebhookConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/watch/mutatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of MutatingWebhookConfiguration. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/watch/mutatingwebhookconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="podtemplate-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">PodTemplate</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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="#deploymentspec-v1-apps">DeploymentSpec [apps/v1]</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="#replicationcontrollerspec-v1-core">ReplicationControllerSpec [core/v1]</a></LI>
<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>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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-podtemplate-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-podtemplate-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a PodTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/podtemplates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-podtemplate-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified PodTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-podtemplate-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified PodTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-podtemplate-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a PodTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-podtemplate-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of PodTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/podtemplates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-podtemplate-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-podtemplate-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified PodTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-podtemplate-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind PodTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/podtemplates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-podtemplate-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind PodTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/podtemplates</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-podtemplate-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind PodTemplate. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/podtemplates/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-podtemplate-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of PodTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/podtemplates</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-podtemplate-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of PodTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/podtemplates</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="poddisruptionbudget-v1-policy">
<H1 class="toc-item resource"><span class="gvk"><span class="k">PodDisruptionBudget</span> <span class="v">v1</span> <span class="g">policy</span></span></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>v1</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-v1-policy">PodDisruptionBudgetList [policy/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#poddisruptionbudgetspec-v1-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-v1-policy">PodDisruptionBudgetStatus</a></I></TD><TD>Most recently observed status of the PodDisruptionBudget.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="poddisruptionbudgetspec-v1-policy">PodDisruptionBudgetSpec v1 policy</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget [policy/v1]</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><BR /><B>patch strategy</B>: <I>replace</I></TD><TD>Label query over pods whose evictions are managed by the disruption budget. A null selector will match no pods, while an empty ({}) selector will select all pods within the namespace.</TD></TR>
<TR><TD><CODE>unhealthyPodEvictionPolicy</CODE><BR /><I>string</I></TD><TD>UnhealthyPodEvictionPolicy defines the criteria for when unhealthy pods should be considered for eviction. Current implementation considers healthy pods, as pods that have status.conditions item with type=&#34;Ready&#34;,status=&#34;True&#34;. Valid policies are IfHealthyBudget and AlwaysAllow. If no policy is specified, the default behavior will be used, which corresponds to the IfHealthyBudget policy. IfHealthyBudget policy means that running pods (status.phase=&#34;Running&#34;), but not yet healthy can be evicted only if the guarded application is not disrupted (status.currentHealthy is at least equal to status.desiredHealthy). Healthy pods will be subject to the PDB for eviction. AlwaysAllow policy means that all running pods (status.phase=&#34;Running&#34;), but not yet healthy are considered disrupted and can be evicted regardless of whether the criteria in a PDB is met. This means perspective running pods of a disrupted application might not get a chance to become healthy. Healthy pods will be subject to the PDB for eviction. Additional policies may be added in the future. Clients making eviction decisions should disallow eviction of unhealthy pods if they encounter an unrecognized policy in this field. This field is beta-level. The eviction API uses this field when the feature gate PDBUnhealthyPodEvictionPolicy is enabled (enabled by default).</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="poddisruptionbudgetstatus-v1-policy">PodDisruptionBudgetStatus v1 policy</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget [policy/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="#condition-v1-meta">Condition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Conditions contain conditions for PDB. The disruption controller sets the DisruptionAllowed condition. The following are known values for the reason field (additional reasons could be added in the future): - SyncFailed: The controller encountered an error and wasn&#39;t able to compute the number of allowed disruptions. Therefore no disruptions are allowed and the status of the condition will be False. - InsufficientPods: The number of pods are either at or below the number required by the PodDisruptionBudget. No disruptions are allowed and the status of the condition will be False. - SufficientPods: There are more pods than required by the PodDisruptionBudget. The condition will be True, and the number of allowed disruptions are provided by the disruptionsAllowed property.</TD></TR>
<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. DisruptionsAllowed and other status information is valid only if observedGeneration equals to PDB&#39;s object generation.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="poddisruptionbudgetlist-v1-policy">PodDisruptionBudgetList v1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a> array</I></TD><TD>Items is a list of PodDisruptionBudgets</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Create</H2>
<P>create a PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Delete</H2>
<P>delete a PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Read</H2>
<P>read the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-policy">PodDisruptionBudgetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/policy/v1/poddisruptionbudgets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-policy">PodDisruptionBudgetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/policy/v1/watch/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/policy/v1/watch/namespaces/{namespace}/poddisruptionbudgets</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of PodDisruptionBudget. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/policy/v1/watch/poddisruptionbudgets</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-poddisruptionbudget-v1-policy">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="priorityclass-v1-scheduling-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">PriorityClass</span> <span class="v">v1</span> <span class="g">scheduling.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>PriorityClass</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="#priorityclasslist-v1-scheduling-k8s-io">PriorityClassList [scheduling/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>preemptionPolicy</CODE><BR /><I>string</I></TD><TD>preemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset.</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>integer</I></TD><TD>value represents the integer 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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="priorityclasslist-v1-scheduling-k8s-io">PriorityClassList v1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#priorityclass-v1-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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a PriorityClass</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/scheduling.k8s.io/v1/priorityclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified PriorityClass</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/scheduling.k8s.io/v1/priorityclasses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified PriorityClass</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/scheduling.k8s.io/v1/priorityclasses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#priorityclass-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a PriorityClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/scheduling.k8s.io/v1/priorityclasses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of PriorityClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/scheduling.k8s.io/v1/priorityclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified PriorityClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/scheduling.k8s.io/v1/priorityclasses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind PriorityClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/scheduling.k8s.io/v1/priorityclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-scheduling-k8s-io">PriorityClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind PriorityClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/scheduling.k8s.io/v1/watch/priorityclasses/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-priorityclass-v1-scheduling-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of PriorityClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/scheduling.k8s.io/v1/watch/priorityclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="resourceclaim-v1beta1-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourceClaim</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ResourceClaim</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="#resourceclaim-v1-core">v1</a>
<a href="#resourceclaim-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaimlist-v1beta1-resource-k8s-io">ResourceClaimList [resource/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/sig-architecture/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/sig-architecture/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="#resourceclaimspec-v1beta1-resource-k8s-io">ResourceClaimSpec</a></I></TD><TD>Spec describes what is being requested and how to configure it. The spec is immutable.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#resourceclaimstatus-v1beta1-resource-k8s-io">ResourceClaimStatus</a></I></TD><TD>Status describes whether the claim is ready to use and what has been allocated.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="resourceclaimspec-v1beta1-resource-k8s-io">ResourceClaimSpec v1beta1 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim [resource/v1beta1]</a></LI>
<LI><a href="#resourceclaimtemplatespec-v1beta1-resource-k8s-io">ResourceClaimTemplateSpec [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#deviceclaim-v1beta1-resource-k8s-io">DeviceClaim</a></I></TD><TD>Devices defines how to request devices.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceclaimstatus-v1beta1-resource-k8s-io">ResourceClaimStatus v1beta1 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allocation</CODE><BR /><I><a href="#allocationresult-v1beta1-resource-k8s-io">AllocationResult</a></I></TD><TD>Allocation is set once the claim has been allocated successfully.</TD></TR>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#allocateddevicestatus-v1beta1-resource-k8s-io">AllocatedDeviceStatus</a> array</I></TD><TD>Devices contains the status of each device allocated for this claim, as reported by the driver. This can include driver-specific information. Entries are owned by their respective drivers.</TD></TR>
<TR><TD><CODE>reservedFor</CODE><BR /><I><a href="#resourceclaimconsumerreference-v1beta1-resource-k8s-io">ResourceClaimConsumerReference</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>uid</I></TD><TD>ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started. A claim that is in use or might be in use because it has been reserved must not get deallocated. In a cluster with multiple scheduler instances, two pods might get scheduled concurrently by different schedulers. When they reference the same ResourceClaim which already has reached its maximum number of consumers, only one pod can be scheduled. Both schedulers try to add their pod to the claim.status.reservedFor field, but only the update that reaches the API server first gets stored. The other one fails with an error and the scheduler which issued it knows that it must put the pod back into the queue, waiting for the ResourceClaim to become usable again. There can be at most 32 such reservations. This may get increased in the future, but not reduced.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceclaimlist-v1beta1-resource-k8s-io">ResourceClaimList v1beta1 resource</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a> array</I></TD><TD>Items is the list of resource claims.</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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimlist-v1beta1-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/resourceclaims</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimlist-v1beta1-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/namespaces/{namespace}/resourceclaims</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/resourceclaims</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="resourceclaimtemplate-v1beta1-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourceClaimTemplate</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ResourceClaimTemplate</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="#resourceclaimtemplate-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaimtemplatelist-v1beta1-resource-k8s-io">ResourceClaimTemplateList [resource/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/sig-architecture/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/sig-architecture/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="#resourceclaimtemplatespec-v1beta1-resource-k8s-io">ResourceClaimTemplateSpec</a></I></TD><TD>Describes the ResourceClaim that is to be generated. This field is immutable. A ResourceClaim will get created by the control plane for a Pod when needed and then not get updated anymore.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="resourceclaimtemplatespec-v1beta1-resource-k8s-io">ResourceClaimTemplateSpec v1beta1 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate [resource/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>ObjectMeta may contain labels and annotations that will be copied into the ResourceClaim when creating it. No other fields are allowed and will be rejected during validation.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#resourceclaimspec-v1beta1-resource-k8s-io">ResourceClaimSpec</a></I></TD><TD>Spec for the ResourceClaim. The entire content is copied unchanged into the ResourceClaim that gets created from this template. The same fields as in a ResourceClaim are also valid here.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceclaimtemplatelist-v1beta1-resource-k8s-io">ResourceClaimTemplateList v1beta1 resource</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a> array</I></TD><TD>Items is the list of resource claim 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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaimtemplates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaimtemplates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaimtemplates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplatelist-v1beta1-resource-k8s-io">ResourceClaimTemplateList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/resourceclaimtemplates</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplatelist-v1beta1-resource-k8s-io">ResourceClaimTemplateList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/namespaces/{namespace}/resourceclaimtemplates</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-resourceclaimtemplate-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/resourceclaimtemplates</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="resourceslice-v1beta1-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourceSlice</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ResourceSlice</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="#resourceslice-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceslicelist-v1beta1-resource-k8s-io">ResourceSliceList [resource/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/sig-architecture/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/sig-architecture/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="#resourceslicespec-v1beta1-resource-k8s-io">ResourceSliceSpec</a></I></TD><TD>Contains the information published by the driver. Changing the spec automatically increments the metadata.generation number.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="resourceslicespec-v1beta1-resource-k8s-io">ResourceSliceSpec v1beta1 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allNodes</CODE><BR /><I>boolean</I></TD><TD>AllNodes indicates that all nodes have access to the resources in the pool. Exactly one of NodeName, NodeSelector and AllNodes must be set.</TD></TR>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#device-v1beta1-resource-k8s-io">Device</a> array</I></TD><TD>Devices lists some or all of the devices in this pool. Must not have more than 128 entries.</TD></TR>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver identifies the DRA driver providing the capacity information. A field selector can be used to list only ResourceSlice objects with a certain driver name. Must be a DNS subdomain and should end with a DNS domain owned by the vendor of the driver. This field is immutable.</TD></TR>
<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>NodeName identifies the node which provides the resources in this pool. A field selector can be used to list only ResourceSlice objects belonging to a certain node. This field can be used to limit access from nodes to ResourceSlices with the same node name. It also indicates to autoscalers that adding new nodes of the same type as some old node might also make new resources available. Exactly one of NodeName, NodeSelector and AllNodes must be set. This field is immutable.</TD></TR>
<TR><TD><CODE>nodeSelector</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>NodeSelector defines which nodes have access to the resources in the pool, when that pool is not limited to a single node. Must use exactly one term. Exactly one of NodeName, NodeSelector and AllNodes must be set.</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I><a href="#resourcepool-v1beta1-resource-k8s-io">ResourcePool</a></I></TD><TD>Pool describes the pool that this ResourceSlice belongs to.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceslicelist-v1beta1-resource-k8s-io">ResourceSliceList v1beta1 resource</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a> array</I></TD><TD>Items is the list of resource ResourceSlices.</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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/resource.k8s.io/v1beta1/resourceslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1beta1/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1beta1/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/resourceslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/resourceslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceslicelist-v1beta1-resource-k8s-io">ResourceSliceList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ResourceSlice. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-resourceslice-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ResourceSlice. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/resourceslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ValidatingAdmissionPolicy</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>ValidatingAdmissionPolicy</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="#validatingadmissionpolicy-v1beta1-admissionregistration-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="#validatingadmissionpolicylist-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList [admissionregistration/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#validatingadmissionpolicyspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec</a></I></TD><TD>Specification of the desired behavior of the ValidatingAdmissionPolicy.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#validatingadmissionpolicystatus-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus</a></I></TD><TD>The status of the ValidatingAdmissionPolicy, including warnings that are useful to determine if the policy behaves in the expected way. Populated by the system. Read-only.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="validatingadmissionpolicyspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec v1 admissionregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>auditAnnotations</CODE><BR /><I><a href="#auditannotation-v1-admissionregistration-k8s-io">AuditAnnotation</a> array</I></TD><TD>auditAnnotations contains CEL expressions which are used to produce audit annotations for the audit event of the API request. validations and auditAnnotations may not both be empty; a least one of validations or auditAnnotations is required.</TD></TR>
<TR><TD><CODE>failurePolicy</CODE><BR /><I>string</I></TD><TD>failurePolicy defines how to handle failures for the admission policy. Failures can occur from CEL expression parse errors, type check errors, runtime errors and invalid or mis-configured policy definitions or bindings. A policy is invalid if spec.paramKind refers to a non-existent Kind. A binding is invalid if spec.paramRef.name refers to a non-existent resource. failurePolicy does not define how validations that evaluate to false are handled. When failurePolicy is set to Fail, ValidatingAdmissionPolicyBinding validationActions define how failures are enforced. Allowed values are Ignore or Fail. Defaults to Fail.</TD></TR>
<TR><TD><CODE>matchConditions</CODE><BR /><I><a href="#matchcondition-v1-admissionregistration-k8s-io">MatchCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>MatchConditions is a list of conditions that must be met for a request to be validated. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed. If a parameter object is provided, it can be accessed via the `params` handle in the same manner as validation expressions. The exact matching logic is (in order): 1. If ANY matchCondition evaluates to FALSE, the policy is skipped. 2. If ALL matchConditions evaluate to TRUE, the policy is evaluated. 3. If any matchCondition evaluates to an error (but none are FALSE): - If failurePolicy=Fail, reject the request - If failurePolicy=Ignore, the policy is skipped</TD></TR>
<TR><TD><CODE>matchConstraints</CODE><BR /><I><a href="#matchresources-v1-admissionregistration-k8s-io">MatchResources</a></I></TD><TD>MatchConstraints specifies what resources this policy is designed to validate. The AdmissionPolicy cares about a request if it matches _all_ Constraints. However, in order to prevent clusters from being put into an unstable state that cannot be recovered from via the API ValidatingAdmissionPolicy cannot match ValidatingAdmissionPolicy and ValidatingAdmissionPolicyBinding. Required.</TD></TR>
<TR><TD><CODE>paramKind</CODE><BR /><I><a href="#paramkind-v1-admissionregistration-k8s-io">ParamKind</a></I></TD><TD>ParamKind specifies the kind of resources used to parameterize this policy. If absent, there are no parameters for this policy and the param CEL variable will not be provided to validation expressions. If ParamKind refers to a non-existent kind, this policy definition is mis-configured and the FailurePolicy is applied. If paramKind is specified but paramRef is unset in ValidatingAdmissionPolicyBinding, the params variable will be null.</TD></TR>
<TR><TD><CODE>validations</CODE><BR /><I><a href="#validation-v1-admissionregistration-k8s-io">Validation</a> array</I></TD><TD>Validations contain CEL expressions which is used to apply the validation. Validations and AuditAnnotations may not both be empty; a minimum of one Validations or AuditAnnotations is required.</TD></TR>
<TR><TD><CODE>variables</CODE><BR /><I><a href="#variable-v1-admissionregistration-k8s-io">Variable</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Variables contain definitions of variables that can be used in composition of other expressions. Each variable is defined as a named CEL expression. The variables defined here will be available under `variables` in other expressions of the policy except MatchConditions because MatchConditions are evaluated before the rest of the policy. The expression of a variable can refer to other variables defined earlier in the list but not those after. Thus, Variables must be sorted by the order of first appearance and acyclic.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="validatingadmissionpolicystatus-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus v1 admissionregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy [admissionregistration/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="#condition-v1-meta">Condition</a> array</I></TD><TD>The conditions represent the latest available observations of a policy&#39;s current state.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The generation observed by the controller.</TD></TR>
<TR><TD><CODE>typeChecking</CODE><BR /><I><a href="#typechecking-v1-admissionregistration-k8s-io">TypeChecking</a></I></TD><TD>The results of type checking for each expression. Presence of this field indicates the completion of the type checking.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="validatingadmissionpolicylist-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList v1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a> array</I></TD><TD>List of ValidatingAdmissionPolicy.</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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicylist-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ValidatingAdmissionPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/watch/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ValidatingAdmissionPolicy. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/watch/validatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-validatingadmissionpolicy-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicies/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ValidatingAdmissionPolicyBinding</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>ValidatingAdmissionPolicyBinding</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="#validatingadmissionpolicybinding-v1beta1-admissionregistration-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="#validatingadmissionpolicybindinglist-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList [admissionregistration/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#validatingadmissionpolicybindingspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec</a></I></TD><TD>Specification of the desired behavior of the ValidatingAdmissionPolicyBinding.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="validatingadmissionpolicybindingspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec v1 admissionregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>matchResources</CODE><BR /><I><a href="#matchresources-v1-admissionregistration-k8s-io">MatchResources</a></I></TD><TD>MatchResources declares what resources match this binding and will be validated by it. Note that this is intersected with the policy&#39;s matchConstraints, so only requests that are matched by the policy can be selected by this. If this is unset, all resources matched by the policy are validated by this binding When resourceRules is unset, it does not constrain resource matching. If a resource is matched by the other fields of this object, it will be validated. Note that this is differs from ValidatingAdmissionPolicy matchConstraints, where resourceRules are required.</TD></TR>
<TR><TD><CODE>paramRef</CODE><BR /><I><a href="#paramref-v1-admissionregistration-k8s-io">ParamRef</a></I></TD><TD>paramRef specifies the parameter resource used to configure the admission control policy. It should point to a resource of the type specified in ParamKind of the bound ValidatingAdmissionPolicy. If the policy specifies a ParamKind and the resource referred to by ParamRef does not exist, this binding is considered mis-configured and the FailurePolicy of the ValidatingAdmissionPolicy applied. If the policy does not specify a ParamKind then this field is ignored, and the rules are evaluated without a param.</TD></TR>
<TR><TD><CODE>policyName</CODE><BR /><I>string</I></TD><TD>PolicyName references a ValidatingAdmissionPolicy name which the ValidatingAdmissionPolicyBinding binds to. If the referenced resource does not exist, this binding is considered invalid and will be ignored Required.</TD></TR>
<TR><TD><CODE>validationActions</CODE><BR /><I>string array</I></TD><TD>validationActions declares how Validations of the referenced ValidatingAdmissionPolicy are enforced. If a validation evaluates to false it is always enforced according to these actions. Failures defined by the ValidatingAdmissionPolicy&#39;s FailurePolicy are enforced according to these actions only if the FailurePolicy is set to Fail, otherwise the failures are ignored. This includes compilation errors, runtime errors and misconfigurations of the policy. validationActions is declared as a set of action values. Order does not matter. validationActions may not contain duplicates of the same action. The supported actions values are: &#34;Deny&#34; specifies that a validation failure results in a denied request. &#34;Warn&#34; specifies that a validation failure is reported to the request client in HTTP Warning headers, with a warning code of 299. Warnings can be sent both for allowed or denied admission responses. &#34;Audit&#34; specifies that a validation failure is included in the published audit event for the request. The audit event will contain a `validation.policy.admission.k8s.io/validation_failure` audit annotation with a value containing the details of the validation failures, formatted as a JSON list of objects, each with the following fields: - message: The validation failure message string - policy: The resource name of the ValidatingAdmissionPolicy - binding: The resource name of the ValidatingAdmissionPolicyBinding - expressionIndex: The index of the failed validations in the ValidatingAdmissionPolicy - validationActions: The enforcement actions enacted for the validation failure Example audit annotation: `&#34;validation.policy.admission.k8s.io/validation_failure&#34;: &#34;[{\&#34;message\&#34;: \&#34;Invalid value\&#34;, {\&#34;policy\&#34;: \&#34;policy.example.com\&#34;, {\&#34;binding\&#34;: \&#34;policybinding.example.com\&#34;, {\&#34;expressionIndex\&#34;: \&#34;1\&#34;, {\&#34;validationActions\&#34;: [\&#34;Audit\&#34;]}]&#34;` Clients should expect to handle additional values by ignoring any values not recognized. &#34;Deny&#34; and &#34;Warn&#34; may not be used together since this combination needlessly duplicates the validation failure both in the API response body and the HTTP warning headers. Required.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="validatingadmissionpolicybindinglist-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList v1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a> array</I></TD><TD>List of PolicyBinding.</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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/validatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicybindinglist-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ValidatingAdmissionPolicyBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/watch/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ValidatingAdmissionPolicyBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/watch/validatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ValidatingWebhookConfiguration</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</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-v1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList [admissionregistration/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>webhooks</CODE><BR /><I><a href="#validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="validatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList v1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#validatingwebhookconfiguration-v1-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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ValidatingWebhookConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/watch/validatingwebhookconfigurations/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-validatingwebhookconfiguration-v1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ValidatingWebhookConfiguration. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1/watch/validatingwebhookconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV id="cluster-apis">
<H1 class="toc-item section resource-category">Cluster</H1>
<P>Cluster resources are responsible for defining configuration of the cluster itself, and are generally only used by cluster operators.</P>
</DIV>
<DIV class="resource-container" id="apiservice-v1-apiregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">APIService</span> <span class="v">v1</span> <span class="g">apiregistration.k8s.io</span></span></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-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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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. If unspecified, system trust roots on the apiserver are used.</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>GroupPriorityMinimum 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 GroupPriorityMinimum 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 class="inline-definition" 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 class="inline-definition" 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/sig-architecture/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>Items is the list of APIService</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create an APIService</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/apiregistration.k8s.io/v1/apiservices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified APIService</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified APIService</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete an APIService</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of APIService</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/apiregistration.k8s.io/v1/apiservices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified APIService</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind APIService</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiregistration.k8s.io/v1/apiservices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind APIService. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiregistration.k8s.io/v1/watch/apiservices/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of APIService. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiregistration.k8s.io/v1/watch/apiservices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified APIService</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/apiregistration.k8s.io/v1/apiservices/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified APIService</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/apiregistration.k8s.io/v1/apiservices/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-apiservice-v1-apiregistration-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified APIService</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/apiregistration.k8s.io/v1/apiservices/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="binding-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Binding</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/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>
<DIV class="operation-category-container" id="write-operations-binding-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-binding-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a Binding</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/bindings</CODE></P>
<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>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="certificatesigningrequest-v1-certificates-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">CertificateSigningRequest</span> <span class="v">v1</span> <span class="g">certificates.k8s.io</span></span></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>v1</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-v1-certificates-k8s-io">CertificateSigningRequestList [certificates/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/sig-architecture/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/sig-architecture/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-v1-certificates-k8s-io">CertificateSigningRequestSpec</a></I></TD><TD>spec contains the certificate request, and is immutable after creation. Only the request, signerName, expirationSeconds, and usages fields can be set on creation. Other fields are derived by Kubernetes and cannot be modified by users.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#certificatesigningrequeststatus-v1-certificates-k8s-io">CertificateSigningRequestStatus</a></I></TD><TD>status contains information about whether the request is approved or denied, and the certificate issued by the signer, or the failure condition indicating signer failure.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="certificatesigningrequestspec-v1-certificates-k8s-io">CertificateSigningRequestSpec v1 certificates</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest [certificates/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expirationSeconds</CODE><BR /><I>integer</I></TD><TD>expirationSeconds is the requested duration of validity of the issued certificate. The certificate signer may issue a certificate with a different validity duration so a client must check the delta between the notBefore and and notAfter fields in the issued certificate to determine the actual duration. The v1.22+ in-tree implementations of the well-known Kubernetes signers will honor this field as long as the requested duration is not greater than the maximum duration they will honor per the --cluster-signing-duration CLI flag to the Kubernetes controller manager. Certificate signers may not honor this field for various reasons: 1. Old signer that is unaware of the field (such as the in-tree implementations prior to v1.22) 2. Signer whose configured maximum is shorter than the requested duration 3. Signer whose configured minimum is longer than the requested duration The minimum valid value for expirationSeconds is 600, i.e. 10 minutes.</TD></TR>
<TR><TD><CODE>extra</CODE><BR /><I>object</I></TD><TD>extra contains extra attributes of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</TD></TR>
<TR><TD><CODE>groups</CODE><BR /><I>string array</I></TD><TD>groups contains group membership of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</TD></TR>
<TR><TD><CODE>request</CODE><BR /><I>string</I></TD><TD>request contains an x509 certificate signing request encoded in a &#34;CERTIFICATE REQUEST&#34; PEM block. When serialized as JSON or YAML, the data is additionally base64-encoded.</TD></TR>
<TR><TD><CODE>signerName</CODE><BR /><I>string</I></TD><TD>signerName indicates the requested signer, and is a qualified name. List/watch requests for CertificateSigningRequests can filter on this field using a &#34;spec.signerName=NAME&#34; fieldSelector. Well-known Kubernetes signers are: 1. &#34;kubernetes.io/kube-apiserver-client&#34;: issues client certificates that can be used to authenticate to kube-apiserver. Requests for this signer are never auto-approved by kube-controller-manager, can be issued by the &#34;csrsigning&#34; controller in kube-controller-manager. 2. &#34;kubernetes.io/kube-apiserver-client-kubelet&#34;: issues client certificates that kubelets use to authenticate to kube-apiserver. Requests for this signer can be auto-approved by the &#34;csrapproving&#34; controller in kube-controller-manager, and can be issued by the &#34;csrsigning&#34; controller in kube-controller-manager. 3. &#34;kubernetes.io/kubelet-serving&#34; issues serving certificates that kubelets use to serve TLS endpoints, which kube-apiserver can connect to securely. Requests for this signer are never auto-approved by kube-controller-manager, and can be issued by the &#34;csrsigning&#34; controller in kube-controller-manager. More details are available at https://k8s.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers Custom signerNames can also be specified. The signer defines: 1. Trust distribution: how trust (CA bundles) are distributed. 2. Permitted subjects: and behavior when a disallowed subject is requested. 3. Required, permitted, or forbidden x509 extensions in the request (including whether subjectAltNames are allowed, which types, restrictions on allowed values) and behavior when a disallowed extension is requested. 4. Required, permitted, or forbidden key usages / extended key usages. 5. Expiration/certificate lifetime: whether it is fixed by the signer, configurable by the admin. 6. Whether or not requests for CA certificates are allowed.</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>uid contains the uid of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</TD></TR>
<TR><TD><CODE>usages</CODE><BR /><I>string array</I></TD><TD>usages specifies a set of key usages requested in the issued certificate. Requests for TLS client certificates typically request: &#34;digital signature&#34;, &#34;key encipherment&#34;, &#34;client auth&#34;. Requests for TLS serving certificates typically request: &#34;key encipherment&#34;, &#34;digital signature&#34;, &#34;server auth&#34;. Valid values are: &#34;signing&#34;, &#34;digital signature&#34;, &#34;content commitment&#34;, &#34;key encipherment&#34;, &#34;key agreement&#34;, &#34;data encipherment&#34;, &#34;cert sign&#34;, &#34;crl sign&#34;, &#34;encipher only&#34;, &#34;decipher only&#34;, &#34;any&#34;, &#34;server auth&#34;, &#34;client auth&#34;, &#34;code signing&#34;, &#34;email protection&#34;, &#34;s/mime&#34;, &#34;ipsec end system&#34;, &#34;ipsec tunnel&#34;, &#34;ipsec user&#34;, &#34;timestamping&#34;, &#34;ocsp signing&#34;, &#34;microsoft sgc&#34;, &#34;netscape sgc&#34;</TD></TR>
<TR><TD><CODE>username</CODE><BR /><I>string</I></TD><TD>username contains the name of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="certificatesigningrequeststatus-v1-certificates-k8s-io">CertificateSigningRequestStatus v1 certificates</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest [certificates/v1]</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>certificate is populated with an issued certificate by the signer after an Approved condition is present. This field is set via the /status subresource. Once populated, this field is immutable. If the certificate signing request is denied, a condition of type &#34;Denied&#34; is added and this field remains empty. If the signer cannot issue the certificate, a condition of type &#34;Failed&#34; is added and this field remains empty. Validation requirements: 1. certificate must contain one or more PEM blocks. 2. All PEM blocks must have the &#34;CERTIFICATE&#34; label, contain no headers, and the encoded data must be a BER-encoded ASN.1 Certificate structure as described in section 4 of RFC5280. 3. Non-PEM content may appear before or after the &#34;CERTIFICATE&#34; PEM blocks and is unvalidated, to allow for explanatory text as described in section 5.2 of RFC7468. If more than one PEM block is present, and the definition of the requested spec.signerName does not indicate otherwise, the first block is the issued certificate, and subsequent blocks should be treated as intermediate certificates and presented in TLS handshakes. The certificate is encoded in PEM format. When serialized as JSON or YAML, the data is additionally base64-encoded, so it consists of: base64( -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- )</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#certificatesigningrequestcondition-v1-certificates-k8s-io">CertificateSigningRequestCondition</a> array</I></TD><TD>conditions applied to the request. Known conditions are &#34;Approved&#34;, &#34;Denied&#34;, and &#34;Failed&#34;.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="certificatesigningrequestlist-v1-certificates-k8s-io">CertificateSigningRequestList v1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a> array</I></TD><TD>items is a collection of CertificateSigningRequest 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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/certificates.k8s.io/v1/certificatesigningrequests</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/certificates.k8s.io/v1/certificatesigningrequests</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/certificates.k8s.io/v1/certificatesigningrequests</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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-v1-certificates-k8s-io">CertificateSigningRequestList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/certificates.k8s.io/v1/watch/certificatesigningrequests/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/certificates.k8s.io/v1/watch/certificatesigningrequests</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-certificatesigningrequest-v1-certificates-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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-v1-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-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="clusterrole-v1-rbac-authorization-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ClusterRole</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></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-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/sig-architecture/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/sig-architecture/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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ClusterRole</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/rbac.authorization.k8s.io/v1/clusterroles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ClusterRole</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ClusterRole</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ClusterRole</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ClusterRole</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterroles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ClusterRole</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ClusterRole</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterroles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ClusterRole. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterroles/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-clusterrole-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ClusterRole. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterroles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="clusterrolebinding-v1-rbac-authorization-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ClusterRoleBinding</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></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-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/sig-architecture/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/sig-architecture/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. This field is immutable.</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/rbac.authorization.k8s.io/v1/clusterrolebindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterrolebindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterrolebindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ClusterRoleBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-clusterrolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ClusterRoleBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="componentstatus-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ComponentStatus</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="read-operations-componentstatus-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-componentstatus-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ComponentStatus</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/componentstatuses/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-componentstatus-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list objects of kind ComponentStatus</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/componentstatuses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="flowschema-v1-flowcontrol-apiserver-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">FlowSchema</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FlowSchema</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="#flowschemalist-v1-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/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/sig-architecture/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/sig-architecture/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&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#flowschemaspec-v1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec</a></I></TD><TD>`spec` is the specification of the desired behavior of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#flowschemastatus-v1-flowcontrol-apiserver-k8s-io">FlowSchemaStatus</a></I></TD><TD>`status` is the current status of a FlowSchema. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="flowschemaspec-v1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec v1 flowcontrol</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>distinguisherMethod</CODE><BR /><I><a href="#flowdistinguishermethod-v1-flowcontrol-apiserver-k8s-io">FlowDistinguisherMethod</a></I></TD><TD>`distinguisherMethod` defines how to compute the flow distinguisher for requests that match this schema. `nil` specifies that the distinguisher is disabled and thus will always be the empty string.</TD></TR>
<TR><TD><CODE>matchingPrecedence</CODE><BR /><I>integer</I></TD><TD>`matchingPrecedence` is used to choose among the FlowSchemas that match a given request. The chosen FlowSchema is among those with the numerically lowest (which we take to be logically highest) MatchingPrecedence. Each MatchingPrecedence value must be ranged in [1,10000]. Note that if the precedence is not specified, it will be set to 1000 as default.</TD></TR>
<TR><TD><CODE>priorityLevelConfiguration</CODE><BR /><I><a href="#prioritylevelconfigurationreference-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationReference</a></I></TD><TD>`priorityLevelConfiguration` should reference a PriorityLevelConfiguration in the cluster. If the reference cannot be resolved, the FlowSchema will be ignored and marked as invalid in its status. Required.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyruleswithsubjects-v1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects</a> array</I></TD><TD>`rules` describes which requests will match this flow schema. This FlowSchema matches a request if and only if at least one member of rules matches the request. if it is an empty slice, there will be no requests matching the FlowSchema.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="flowschemastatus-v1-flowcontrol-apiserver-k8s-io">FlowSchemaStatus v1 flowcontrol</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/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="#flowschemacondition-v1-flowcontrol-apiserver-k8s-io">FlowSchemaCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>`conditions` is a list of the current states of FlowSchema.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="flowschemalist-v1-flowcontrol-apiserver-k8s-io">FlowSchemaList v1 flowcontrol</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a> array</I></TD><TD>`items` is a list of FlowSchemas.</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/sig-architecture/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. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#flowschemalist-v1-flowcontrol-apiserver-k8s-io">FlowSchemaList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind FlowSchema. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/watch/flowschemas/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of FlowSchema. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/watch/flowschemas</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-flowschema-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified FlowSchema</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the FlowSchema</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="ipaddress-v1beta1-networking-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">IPAddress</span> <span class="v">v1beta1</span> <span class="g">networking.k8s.io</span></span></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>v1beta1</CODE></TD><TD><CODE>IPAddress</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="#ipaddresslist-v1beta1-networking-k8s-io">IPAddressList [networking/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#ipaddressspec-v1beta1-networking-k8s-io">IPAddressSpec</a></I></TD><TD>spec is the desired state of the IPAddress. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="ipaddressspec-v1beta1-networking-k8s-io">IPAddressSpec v1beta1 networking</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress [networking/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>parentRef</CODE><BR /><I><a href="#parentreference-v1beta1-networking-k8s-io">ParentReference</a></I></TD><TD>ParentRef references the resource that an IPAddress is attached to. An IPAddress must reference a parent object.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="ipaddresslist-v1beta1-networking-k8s-io">IPAddressList v1beta1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a> array</I></TD><TD>items is the list of IPAddresses.</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create an IPAddress</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/networking.k8s.io/v1beta1/ipaddresses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified IPAddress</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/networking.k8s.io/v1beta1/ipaddresses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified IPAddress</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/networking.k8s.io/v1beta1/ipaddresses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete an IPAddress</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1beta1/ipaddresses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of IPAddress</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1beta1/ipaddresses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified IPAddress</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1beta1/ipaddresses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind IPAddress</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1beta1/ipaddresses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ipaddresslist-v1beta1-networking-k8s-io">IPAddressList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind IPAddress. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1beta1/watch/ipaddresses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the IPAddress</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-ipaddress-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of IPAddress. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1beta1/watch/ipaddresses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="lease-v1-coordination-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Lease</span> <span class="v">v1</span> <span class="g">coordination.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>coordination.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Lease</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="#leaselist-v1-coordination-k8s-io">LeaseList [coordination/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#leasespec-v1-coordination-k8s-io">LeaseSpec</a></I></TD><TD>spec contains the specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="leasespec-v1-coordination-k8s-io">LeaseSpec v1 coordination</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#lease-v1-coordination-k8s-io">Lease [coordination/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>acquireTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>acquireTime is a time when the current lease was acquired.</TD></TR>
<TR><TD><CODE>holderIdentity</CODE><BR /><I>string</I></TD><TD>holderIdentity contains the identity of the holder of a current lease. If Coordinated Leader Election is used, the holder identity must be equal to the elected LeaseCandidate.metadata.name field.</TD></TR>
<TR><TD><CODE>leaseDurationSeconds</CODE><BR /><I>integer</I></TD><TD>leaseDurationSeconds is a duration that candidates for a lease need to wait to force acquire it. This is measured against the time of last observed renewTime.</TD></TR>
<TR><TD><CODE>leaseTransitions</CODE><BR /><I>integer</I></TD><TD>leaseTransitions is the number of transitions of a lease between holders.</TD></TR>
<TR><TD><CODE>preferredHolder</CODE><BR /><I>string</I></TD><TD>PreferredHolder signals to a lease holder that the lease has a more optimal holder and should be given up. This field can only be set if Strategy is also set.</TD></TR>
<TR><TD><CODE>renewTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>renewTime is a time when the current holder of a lease has last updated the lease.</TD></TR>
<TR><TD><CODE>strategy</CODE><BR /><I>string</I></TD><TD>Strategy indicates the strategy for picking the leader for coordinated leader election. If the field is not specified, there is no active coordination for this lease. (Alpha) Using this field requires the CoordinatedLeaderElection feature gate to be enabled.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="leaselist-v1-coordination-k8s-io">LeaseList v1 coordination</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#lease-v1-coordination-k8s-io">Lease</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a Lease</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Lease</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Lease</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a Lease</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Lease</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Lease</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#lease-v1-coordination-k8s-io">Lease</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Lease</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1/namespaces/{namespace}/leases</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#leaselist-v1-coordination-k8s-io">LeaseList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Lease</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1/leases</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#leaselist-v1-coordination-k8s-io">LeaseList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Lease. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1/watch/namespaces/{namespace}/leases/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Lease</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Lease. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1/watch/namespaces/{namespace}/leases</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-lease-v1-coordination-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Lease. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1/watch/leases</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="leasecandidate-v1alpha2-coordination-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">LeaseCandidate</span> <span class="v">v1alpha2</span> <span class="g">coordination.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>coordination.k8s.io</CODE></TD><TD><CODE>v1alpha2</CODE></TD><TD><CODE>LeaseCandidate</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="#leasecandidatelist-v1alpha2-coordination-k8s-io">LeaseCandidateList [coordination/v1alpha2]</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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#leasecandidatespec-v1alpha2-coordination-k8s-io">LeaseCandidateSpec</a></I></TD><TD>spec contains the specification of the Lease. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="leasecandidatespec-v1alpha2-coordination-k8s-io">LeaseCandidateSpec v1alpha2 coordination</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate [coordination/v1alpha2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>binaryVersion</CODE><BR /><I>string</I></TD><TD>BinaryVersion is the binary version. It must be in a semver format without leading `v`. This field is required.</TD></TR>
<TR><TD><CODE>emulationVersion</CODE><BR /><I>string</I></TD><TD>EmulationVersion is the emulation version. It must be in a semver format without leading `v`. EmulationVersion must be less than or equal to BinaryVersion. This field is required when strategy is &#34;OldestEmulationVersion&#34;</TD></TR>
<TR><TD><CODE>leaseName</CODE><BR /><I>string</I></TD><TD>LeaseName is the name of the lease for which this candidate is contending. This field is immutable.</TD></TR>
<TR><TD><CODE>pingTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>PingTime is the last time that the server has requested the LeaseCandidate to renew. It is only done during leader election to check if any LeaseCandidates have become ineligible. When PingTime is updated, the LeaseCandidate will respond by updating RenewTime.</TD></TR>
<TR><TD><CODE>renewTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>RenewTime is the time that the LeaseCandidate was last updated. Any time a Lease needs to do leader election, the PingTime field is updated to signal to the LeaseCandidate that they should update the RenewTime. Old LeaseCandidate objects are also garbage collected if it has been hours since the last renew. The PingTime field is updated regularly to prevent garbage collection for still active LeaseCandidates.</TD></TR>
<TR><TD><CODE>strategy</CODE><BR /><I>string</I></TD><TD>Strategy is the strategy that coordinated leader election will use for picking the leader. If multiple candidates for the same Lease return different strategies, the strategy provided by the candidate with the latest BinaryVersion will be used. If there is still conflict, this is a user error and coordinated leader election will not operate the Lease until resolved. (Alpha) Using this field requires the CoordinatedLeaderElection feature gate to be enabled.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="leasecandidatelist-v1alpha2-coordination-k8s-io">LeaseCandidateList v1alpha2 coordination</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a LeaseCandidate</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/coordination.k8s.io/v1alpha2/namespaces/{namespace}/leasecandidates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified LeaseCandidate</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/coordination.k8s.io/v1alpha2/namespaces/{namespace}/leasecandidates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LeaseCandidate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified LeaseCandidate</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/coordination.k8s.io/v1alpha2/namespaces/{namespace}/leasecandidates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LeaseCandidate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a LeaseCandidate</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/coordination.k8s.io/v1alpha2/namespaces/{namespace}/leasecandidates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LeaseCandidate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of LeaseCandidate</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/coordination.k8s.io/v1alpha2/namespaces/{namespace}/leasecandidates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified LeaseCandidate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1alpha2/namespaces/{namespace}/leasecandidates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LeaseCandidate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind LeaseCandidate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1alpha2/namespaces/{namespace}/leasecandidates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#leasecandidatelist-v1alpha2-coordination-k8s-io">LeaseCandidateList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind LeaseCandidate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1alpha2/leasecandidates</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#leasecandidatelist-v1alpha2-coordination-k8s-io">LeaseCandidateList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind LeaseCandidate. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1alpha2/watch/namespaces/{namespace}/leasecandidates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LeaseCandidate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of LeaseCandidate. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1alpha2/watch/namespaces/{namespace}/leasecandidates</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-leasecandidate-v1alpha2-coordination-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of LeaseCandidate. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/coordination.k8s.io/v1alpha2/watch/leasecandidates</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="localsubjectaccessreview-v1-authorization-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">LocalSubjectAccessReview</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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>
<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/sig-architecture/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/sig-architecture/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 list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</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>
<DIV class="operation-category-container" id="write-operations-localsubjectaccessreview-v1-authorization-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-localsubjectaccessreview-v1-authorization-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a LocalSubjectAccessReview</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/authorization.k8s.io/v1/namespaces/{namespace}/localsubjectaccessreviews</CODE></P>
<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>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>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>200<br /><I><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>OK</TD></TR>
<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>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="namespace-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Namespace</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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 class="inline-definition" 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>conditions</CODE><BR /><I><a href="#namespacecondition-v1-core">NamespaceCondition</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 namespace&#39;s current state.</TD></TR>
<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 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-namespace-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-namespace-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a Namespace</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-namespace-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Namespace</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-namespace-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Namespace</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-namespace-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a Namespace</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-namespace-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-namespace-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Namespace</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-namespace-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Namespace</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-namespace-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Namespace. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-namespace-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Namespace. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-namespace-v1-core">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-namespace-v1-core">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified Namespace</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-namespace-v1-core">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified Namespace</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-namespace-v1-core">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified Namespace</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="node-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Node</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>Deprecated: Previously used to specify the source of the node&#39;s configuration for the DynamicKubeletConfig feature. This feature is removed.</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>podCIDRs</CODE><BR /><I>string array</I><BR /><B>patch strategy</B>: <I>merge</I></TD><TD>podCIDRs represents the IP ranges assigned to the node for usage by Pods on that node. If this field is specified, the 0th entry must match the podCIDR field. It may contain at most 1 value for each of IPv4 and IPv6.</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 class="inline-definition" 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/reference/node/node-status/#addresses Note: This field is declared as mergeable, but the merge key is not sufficiently unique, which can cause data corruption when it is merged. Callers should instead use a full-replacement patch. See https://pr.k8s.io/79391 for an example. Consumers should assume that addresses can change during the lifetime of a Node. However, there are some exceptions where this may not be possible, such as Pods that inherit a Node&#39;s address in its own status or consumers of the downward API (status.hostIP).</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/reference/node/node-status/#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/reference/node/node-status/#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>features</CODE><BR /><I><a href="#nodefeatures-v1-core">NodeFeatures</a></I></TD><TD>Features describes the set of features implemented by the CRI implementation.</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/reference/node/node-status/#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>runtimeHandlers</CODE><BR /><I><a href="#noderuntimehandler-v1-core">NodeRuntimeHandler</a> array</I></TD><TD>The available runtime handlers.</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 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-node-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-node-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a Node</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/nodes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-node-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Node</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/nodes/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-node-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Node</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/nodes/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-node-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a Node</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/nodes/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-node-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Node</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/nodes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-node-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-node-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Node</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/nodes/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-node-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Node</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/nodes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-node-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Node. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/nodes/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-node-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Node. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/nodes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-node-v1-core">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-node-v1-core">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified Node</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/nodes/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-node-v1-core">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified Node</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/nodes/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-node-v1-core">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified Node</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/nodes/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="proxy-operations-node-v1-core">
<H2 class="toc-item operation-category">Proxy Operations</H2>
<DIV class="operation-container" id="create-connect-proxy-node-v1-core">
<H2 class="toc-item operation">Create Connect Proxy</H2>
<P>connect POST requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/nodes/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
<DIV class="operation-container" id="create-connect-proxy-path-node-v1-core">
<H2 class="toc-item operation">Create Connect Proxy Path</H2>
<P>connect POST requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/nodes/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
<DIV class="operation-container" id="delete-connect-proxy-node-v1-core">
<H2 class="toc-item operation">Delete Connect Proxy</H2>
<P>connect DELETE requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/nodes/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
<DIV class="operation-container" id="delete-connect-proxy-path-node-v1-core">
<H2 class="toc-item operation">Delete Connect Proxy Path</H2>
<P>connect DELETE requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/nodes/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
<DIV class="operation-container" id="get-connect-proxy-node-v1-core">
<H2 class="toc-item operation">Get Connect Proxy</H2>
<P>connect GET requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/nodes/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
<DIV class="operation-container" id="get-connect-proxy-path-node-v1-core">
<H2 class="toc-item operation">Get Connect Proxy Path</H2>
<P>connect GET requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/nodes/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
<DIV class="operation-container" id="head-connect-proxy-node-v1-core">
<H2 class="toc-item operation">Head Connect Proxy</H2>
<P>connect HEAD requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>HEAD /api/v1/nodes/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
<DIV class="operation-container" id="head-connect-proxy-path-node-v1-core">
<H2 class="toc-item operation">Head Connect Proxy Path</H2>
<P>connect HEAD requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>HEAD /api/v1/nodes/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
<DIV class="operation-container" id="replace-connect-proxy-node-v1-core">
<H2 class="toc-item operation">Replace Connect Proxy</H2>
<P>connect PUT requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/nodes/{name}/proxy</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
<DIV class="operation-container" id="replace-connect-proxy-path-node-v1-core">
<H2 class="toc-item operation">Replace Connect Proxy Path</H2>
<P>connect PUT requests to proxy of Node</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/nodes/{name}/proxy/{path}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NodeProxyOptions</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="persistentvolume-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">PersistentVolume</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>
<LI><a href="#volumeattachmentsource-v1-storage-k8s-io">VolumeAttachmentSource [storage/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. Deprecated: AWSElasticBlockStore is deprecated. All operations for the in-tree awsElasticBlockStore type are redirected to the ebs.csi.aws.com CSI driver. 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. Deprecated: AzureDisk is deprecated. All operations for the in-tree azureDisk type are redirected to the disk.csi.azure.com CSI driver.</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. Deprecated: AzureFile is deprecated. All operations for the in-tree azureFile type are redirected to the file.csi.azure.com CSI driver.</TD></TR>
<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>capacity is the 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. Deprecated: CephFS is deprecated and the in-tree cephfs type is no longer supported.</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. Deprecated: Cinder is deprecated. All operations for the in-tree cinder type are redirected to the cinder.csi.openstack.org CSI driver. More info: https://examples.k8s.io/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 is handled by an external CSI driver.</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. Deprecated: FlexVolume is deprecated. Consider using a CSIDriver instead.</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. Deprecated: Flocker is deprecated and the in-tree flocker type is no longer supported.</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. Deprecated: GCEPersistentDisk is deprecated. All operations for the in-tree gcePersistentDisk type are redirected to the pd.csi.storage.gke.io CSI driver. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
<TR><TD><CODE>glusterfs</CODE><BR /><I><a href="#glusterfspersistentvolumesource-v1-core">GlusterfsPersistentVolumeSource</a></I></TD><TD>glusterfs represents a Glusterfs volume that is attached to a host and exposed to the pod. Provisioned by an admin. Deprecated: Glusterfs is deprecated and the in-tree glusterfs type is no longer supported. More info: https://examples.k8s.io/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>mountOptions is the 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>persistentVolumeReclaimPolicy defines 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. Deprecated: PhotonPersistentDisk is deprecated and the in-tree photonPersistentDisk type is no longer supported.</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. Deprecated: PortworxVolume is deprecated. All operations for the in-tree portworxVolume type are redirected to the pxd.portworx.com CSI driver when the CSIMigrationPortworx feature-gate is on.</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. Deprecated: Quobyte is deprecated and the in-tree quobyte type is no longer supported.</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. Deprecated: RBD is deprecated and the in-tree rbd type is no longer supported. More info: https://examples.k8s.io/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. Deprecated: ScaleIO is deprecated and the in-tree scaleIO type is no longer supported.</TD></TR>
<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>storageClassName is the 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. Deprecated: StorageOS is deprecated and the in-tree storageos type is no longer supported. More info: https://examples.k8s.io/volumes/storageos/README.md</TD></TR>
<TR><TD><CODE>volumeAttributesClassName</CODE><BR /><I>string</I></TD><TD>Name of VolumeAttributesClass to which this persistent volume belongs. Empty value is not allowed. When this field is not set, it indicates that this volume does not belong to any VolumeAttributesClass. This field is mutable and can be changed by the CSI driver after a volume has been updated successfully to a new class. For an unbound PersistentVolume, the volumeAttributesClassName will be matched with unbound PersistentVolumeClaims during the binding process. This is a beta field and requires enabling VolumeAttributesClass feature (off by default).</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.</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. Deprecated: VsphereVolume is deprecated. All operations for the in-tree vsphereVolume type are redirected to the csi.vsphere.vmware.com CSI driver.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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>lastPhaseTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastPhaseTransitionTime is the time the phase transitioned from one to another and automatically resets to current time everytime a volume phase transitions.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is 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 class="inline-definition" 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#persistentvolume-v1-core">PersistentVolume</a> array</I></TD><TD>items is a 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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-persistentvolume-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-persistentvolume-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/persistentvolumes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-persistentvolume-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/persistentvolumes/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-persistentvolume-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/persistentvolumes/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-persistentvolume-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/persistentvolumes/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-persistentvolume-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/persistentvolumes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-persistentvolume-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-persistentvolume-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/persistentvolumes/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-persistentvolume-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/persistentvolumes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-persistentvolume-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind PersistentVolume. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/persistentvolumes/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-persistentvolume-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of PersistentVolume. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/persistentvolumes</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-persistentvolume-v1-core">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-persistentvolume-v1-core">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/persistentvolumes/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-persistentvolume-v1-core">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/persistentvolumes/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-persistentvolume-v1-core">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/persistentvolumes/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">PriorityLevelConfiguration</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PriorityLevelConfiguration</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="#prioritylevelconfigurationlist-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/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/sig-architecture/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/sig-architecture/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&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#prioritylevelconfigurationspec-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec</a></I></TD><TD>`spec` is the specification of the desired behavior of a &#34;request-priority&#34;. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#prioritylevelconfigurationstatus-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus</a></I></TD><TD>`status` is the current status of a &#34;request-priority&#34;. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="prioritylevelconfigurationspec-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec v1 flowcontrol</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>exempt</CODE><BR /><I><a href="#exemptprioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">ExemptPriorityLevelConfiguration</a></I></TD><TD>`exempt` specifies how requests are handled for an exempt priority level. This field MUST be empty if `type` is `&#34;Limited&#34;`. This field MAY be non-empty if `type` is `&#34;Exempt&#34;`. If empty and `type` is `&#34;Exempt&#34;` then the default values for `ExemptPriorityLevelConfiguration` apply.</TD></TR>
<TR><TD><CODE>limited</CODE><BR /><I><a href="#limitedprioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration</a></I></TD><TD>`limited` specifies how requests are handled for a Limited priority level. This field must be non-empty if and only if `type` is `&#34;Limited&#34;`.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` indicates whether this priority level is subject to limitation on request execution. A value of `&#34;Exempt&#34;` means that requests of this priority level are not subject to a limit (and thus are never queued) and do not detract from the capacity made available to other priority levels. A value of `&#34;Limited&#34;` means that (a) requests of this priority level _are_ subject to limits and (b) some of the server&#39;s limited capacity is made available exclusively to this priority level. Required.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="prioritylevelconfigurationstatus-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus v1 flowcontrol</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/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="#prioritylevelconfigurationcondition-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>`conditions` is the current state of &#34;request-priority&#34;.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="prioritylevelconfigurationlist-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList v1 flowcontrol</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a> array</I></TD><TD>`items` is a list of request-priorities.</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/sig-architecture/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 object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#prioritylevelconfigurationlist-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind PriorityLevelConfiguration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/watch/prioritylevelconfigurations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of PriorityLevelConfiguration. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/watch/prioritylevelconfigurations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified PriorityLevelConfiguration</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityLevelConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="resourcequota-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourceQuota</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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 class="inline-definition" 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 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-resourcequota-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-resourcequota-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/resourcequotas</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-resourcequota-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-resourcequota-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-resourcequota-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-resourcequota-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/resourcequotas</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-resourcequota-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-resourcequota-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-resourcequota-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/resourcequotas</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-resourcequota-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/resourcequotas</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-resourcequota-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ResourceQuota. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/resourcequotas/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-resourcequota-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ResourceQuota. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/resourcequotas</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-resourcequota-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ResourceQuota. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/resourcequotas</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-resourcequota-v1-core">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-resourcequota-v1-core">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-resourcequota-v1-core">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-resourcequota-v1-core">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="role-v1-rbac-authorization-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Role</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></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-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/sig-architecture/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/sig-architecture/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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a Role</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="patch-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Role</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Role</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a Role</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Role</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Role</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Role</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Role</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/roles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Role. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/roles/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Role. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/roles</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-role-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Role. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/roles</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="rolebinding-v1-rbac-authorization-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">RoleBinding</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></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-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/sig-architecture/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/sig-architecture/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. This field is immutable.</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a RoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified RoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified RoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a RoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of RoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified RoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind RoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind RoleBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/rolebindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind RoleBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/rolebindings/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of RoleBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/rolebindings</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of RoleBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/rolebindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="runtimeclass-v1-node-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">RuntimeClass</span> <span class="v">v1</span> <span class="g">node.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RuntimeClass</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="#runtimeclasslist-v1-node-k8s-io">RuntimeClassList [node/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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>handler</CODE><BR /><I>string</I></TD><TD>handler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node &amp; CRI configuration. It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called &#34;runc&#34; might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The Handler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.</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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1-node-k8s-io">Overhead</a></I></TD><TD>overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://kubernetes.io/docs/concepts/scheduling-eviction/pod-overhead/</TD></TR>
<TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1-node-k8s-io">Scheduling</a></I></TD><TD>scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="runtimeclasslist-v1-node-k8s-io">RuntimeClassList v1 node</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a RuntimeClass</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/node.k8s.io/v1/runtimeclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified RuntimeClass</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/node.k8s.io/v1/runtimeclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified RuntimeClass</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/node.k8s.io/v1/runtimeclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a RuntimeClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/node.k8s.io/v1/runtimeclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of RuntimeClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/node.k8s.io/v1/runtimeclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified RuntimeClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/node.k8s.io/v1/runtimeclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind RuntimeClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/node.k8s.io/v1/runtimeclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#runtimeclasslist-v1-node-k8s-io">RuntimeClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/node.k8s.io/v1/watch/runtimeclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RuntimeClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-runtimeclass-v1-node-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of RuntimeClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/node.k8s.io/v1/watch/runtimeclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="selfsubjectaccessreview-v1-authorization-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">SelfSubjectAccessReview</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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>
<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/sig-architecture/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/sig-architecture/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 list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>
</DIV>
<DIV class="operation-category-container" id="write-operations-selfsubjectaccessreview-v1-authorization-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-selfsubjectaccessreview-v1-authorization-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a SelfSubjectAccessReview</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/authorization.k8s.io/v1/selfsubjectaccessreviews</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="selfsubjectreview-v1-authentication-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">SelfSubjectReview</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></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>SelfSubjectReview</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="#selfsubjectreview-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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#selfsubjectreviewstatus-v1-authentication-k8s-io">SelfSubjectReviewStatus</a></I></TD><TD>Status is filled in by the server with the user attributes.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="selfsubjectreviewstatus-v1-authentication-k8s-io">SelfSubjectReviewStatus v1 authentication</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectreview-v1-authentication-k8s-io">SelfSubjectReview [authentication/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>userInfo</CODE><BR /><I><a href="#userinfo-v1-authentication-k8s-io">UserInfo</a></I></TD><TD>User attributes of the user making this request.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-selfsubjectreview-v1-authentication-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-selfsubjectreview-v1-authentication-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a SelfSubjectReview</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/authentication.k8s.io/v1/selfsubjectreviews</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#selfsubjectreview-v1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#selfsubjectreview-v1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#selfsubjectreview-v1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#selfsubjectreview-v1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="selfsubjectrulesreview-v1-authorization-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">SelfSubjectRulesReview</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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>
<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/sig-architecture/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/sig-architecture/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 list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>
</DIV>
<DIV class="operation-category-container" id="write-operations-selfsubjectrulesreview-v1-authorization-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-selfsubjectrulesreview-v1-authorization-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a SelfSubjectRulesReview</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="serviceaccount-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ServiceAccount</span> <span class="v">v1</span> <span class="g">core</span></span></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/sig-architecture/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/sig-architecture/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/sig-architecture/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 a list of the secrets in the same namespace that pods running using this ServiceAccount are allowed to use. Pods are only limited to this list if this service account has a &#34;kubernetes.io/enforce-mountable-secrets&#34; annotation set to &#34;true&#34;. The &#34;kubernetes.io/enforce-mountable-secrets&#34; annotation is deprecated since v1.32. Prefer separate namespaces to isolate access to mounted secrets. This field should not be used to find auto-generated service account token secrets for use outside of pods. Instead, tokens can be requested directly using the TokenRequest API, or service account token secrets can be manually created. More info: https://kubernetes.io/docs/concepts/configuration/secret</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-serviceaccount-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-serviceaccount-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create a ServiceAccount</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/serviceaccounts</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-serviceaccount-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ServiceAccount</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-serviceaccount-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ServiceAccount</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-serviceaccount-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ServiceAccount</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-serviceaccount-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ServiceAccount</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/serviceaccounts</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-serviceaccount-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-serviceaccount-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ServiceAccount</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-serviceaccount-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ServiceAccount</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/serviceaccounts</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-serviceaccount-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ServiceAccount</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/serviceaccounts</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-serviceaccount-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ServiceAccount. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/serviceaccounts/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-serviceaccount-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ServiceAccount. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/serviceaccounts</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-serviceaccount-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ServiceAccount. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/serviceaccounts</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="servicecidr-v1beta1-networking-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ServiceCIDR</span> <span class="v">v1beta1</span> <span class="g">networking.k8s.io</span></span></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>v1beta1</CODE></TD><TD><CODE>ServiceCIDR</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="#servicecidrlist-v1beta1-networking-k8s-io">ServiceCIDRList [networking/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#servicecidrspec-v1beta1-networking-k8s-io">ServiceCIDRSpec</a></I></TD><TD>spec is the desired state of the ServiceCIDR. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#servicecidrstatus-v1beta1-networking-k8s-io">ServiceCIDRStatus</a></I></TD><TD>status represents the current state of the ServiceCIDR. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="servicecidrspec-v1beta1-networking-k8s-io">ServiceCIDRSpec v1beta1 networking</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR [networking/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>cidrs</CODE><BR /><I>string array</I></TD><TD>CIDRs defines the IP blocks in CIDR notation (e.g. &#34;192.168.0.0/24&#34; or &#34;2001:db8::/64&#34;) from which to assign service cluster IPs. Max of two CIDRs is allowed, one of each IP family. This field is immutable.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="servicecidrstatus-v1beta1-networking-k8s-io">ServiceCIDRStatus v1beta1 networking</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR [networking/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="#condition-v1-meta">Condition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>conditions holds an array of metav1.Condition that describe the state of the ServiceCIDR. Current service state</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="servicecidrlist-v1beta1-networking-k8s-io">ServiceCIDRList v1beta1 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a> array</I></TD><TD>items is the list of ServiceCIDRs.</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/networking.k8s.io/v1beta1/servicecidrs</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/networking.k8s.io/v1beta1/servicecidrs/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceCIDR</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/networking.k8s.io/v1beta1/servicecidrs/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceCIDR</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1beta1/servicecidrs/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceCIDR</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1beta1/servicecidrs</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1beta1/servicecidrs/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceCIDR</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1beta1/servicecidrs</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#servicecidrlist-v1beta1-networking-k8s-io">ServiceCIDRList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ServiceCIDR. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1beta1/watch/servicecidrs/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceCIDR</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ServiceCIDR. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1beta1/watch/servicecidrs</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/networking.k8s.io/v1beta1/servicecidrs/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceCIDR</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1beta1/servicecidrs/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceCIDR</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-servicecidr-v1beta1-networking-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified ServiceCIDR</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/networking.k8s.io/v1beta1/servicecidrs/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceCIDR</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="storageversion-v1alpha1-internal-apiserver-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">StorageVersion</span> <span class="v">v1alpha1</span> <span class="g">internal.apiserver.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>internal.apiserver.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>StorageVersion</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="#storageversionlist-v1alpha1-internal-apiserver-k8s-io">StorageVersionList [apiserverinternal/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>The name is &lt;group&gt;.&lt;resource&gt;.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#storageversionspec-v1alpha1-internal-apiserver-k8s-io">StorageVersionSpec</a></I></TD><TD>Spec is an empty spec. It is here to comply with Kubernetes API style.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#storageversionstatus-v1alpha1-internal-apiserver-k8s-io">StorageVersionStatus</a></I></TD><TD>API server instances report the version they can decode and the version they encode objects to when persisting objects in the backend.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="storageversionspec-v1alpha1-internal-apiserver-k8s-io">StorageVersionSpec v1alpha1 apiserverinternal</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion [apiserverinternal/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="storageversionstatus-v1alpha1-internal-apiserver-k8s-io">StorageVersionStatus v1alpha1 apiserverinternal</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion [apiserverinternal/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>commonEncodingVersion</CODE><BR /><I>string</I></TD><TD>If all API server instances agree on the same encoding storage version, then this field is set to that version. Otherwise this field is left empty. API servers should finish updating its storageVersionStatus entry before serving write operations, so that this field will be in sync with the reality.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#storageversioncondition-v1alpha1-internal-apiserver-k8s-io">StorageVersionCondition</a> array</I></TD><TD>The latest available observations of the storageVersion&#39;s state.</TD></TR>
<TR><TD><CODE>storageVersions</CODE><BR /><I><a href="#serverstorageversion-v1alpha1-internal-apiserver-k8s-io">ServerStorageVersion</a> array</I></TD><TD>The reported versions per API server instance.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="storageversionlist-v1alpha1-internal-apiserver-k8s-io">StorageVersionList v1alpha1 apiserverinternal</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a> array</I></TD><TD>Items holds a list of StorageVersion</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/internal.apiserver.k8s.io/v1alpha1/storageversions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/internal.apiserver.k8s.io/v1alpha1/storageversions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/storageversions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionlist-v1alpha1-internal-apiserver-k8s-io">StorageVersionList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind StorageVersion. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/watch/storageversions/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of StorageVersion. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/watch/storageversions</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-storageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified StorageVersion</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/internal.apiserver.k8s.io/v1alpha1/storageversions/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersion</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">StorageVersionMigration</span> <span class="v">v1alpha1</span> <span class="g">storagemigration.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storagemigration.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>StorageVersionMigration</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="#storageversionmigrationlist-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationList [storagemigration/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#storageversionmigrationspec-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationSpec</a></I></TD><TD>Specification of the migration.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#storageversionmigrationstatus-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationStatus</a></I></TD><TD>Status of the migration.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="storageversionmigrationspec-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationSpec v1alpha1 storagemigration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration [storagemigration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continueToken</CODE><BR /><I>string</I></TD><TD>The token used in the list options to get the next chunk of objects to migrate. When the .status.conditions indicates the migration is &#34;Running&#34;, users can use this token to check the progress of the migration.</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I><a href="#groupversionresource-v1alpha1-storagemigration-k8s-io">GroupVersionResource</a></I></TD><TD>The resource that is being migrated. The migrator sends requests to the endpoint serving the resource. Immutable.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="storageversionmigrationstatus-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationStatus v1alpha1 storagemigration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration [storagemigration/v1alpha1]</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="#migrationcondition-v1alpha1-storagemigration-k8s-io">MigrationCondition</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 the migration&#39;s current state.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>ResourceVersion to compare with the GC cache for performing the migration. This is the current resource version of given group, version and resource when kube-controller-manager first observes this StorageVersionMigration resource.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="storageversionmigrationlist-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationList v1alpha1 storagemigration</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Items is the list of StorageVersionMigration</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigrationlist-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind StorageVersionMigration. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/watch/storageversionmigrations/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of StorageVersionMigration. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/watch/storageversionmigrations</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-storageversionmigration-v1alpha1-storagemigration-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified StorageVersionMigration</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageVersionMigration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="subjectaccessreview-v1-authorization-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">SubjectAccessReview</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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>
<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/sig-architecture/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/sig-architecture/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 list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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 class="inline-definition" 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>
</DIV>
<DIV class="operation-category-container" id="write-operations-subjectaccessreview-v1-authorization-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-subjectaccessreview-v1-authorization-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a SubjectAccessReview</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/authorization.k8s.io/v1/subjectaccessreviews</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>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>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>
<TR><TD>202<br /><I><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="tokenrequest-v1-authentication-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">TokenRequest</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></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>TokenRequest</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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#tokenrequestspec-v1-authentication-k8s-io">TokenRequestSpec</a></I></TD><TD>Spec holds information about the request being evaluated</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#tokenrequeststatus-v1-authentication-k8s-io">TokenRequestStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the token can be authenticated.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="tokenrequestspec-v1-authentication-k8s-io">TokenRequestSpec v1 authentication</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#tokenrequest-v1-authentication-k8s-io">TokenRequest [authentication/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>audiences</CODE><BR /><I>string array</I></TD><TD>Audiences are the intendend audiences of the token. A recipient of a token must identify themself with an identifier in the list of audiences of the token, and otherwise should reject the token. A token issued for multiple audiences may be used to authenticate against any of the audiences listed but implies a high degree of trust between the target audiences.</TD></TR>
<TR><TD><CODE>boundObjectRef</CODE><BR /><I><a href="#boundobjectreference-v1-authentication-k8s-io">BoundObjectReference</a></I></TD><TD>BoundObjectRef is a reference to an object that the token will be bound to. The token will only be valid for as long as the bound object exists. NOTE: The API server&#39;s TokenReview endpoint will validate the BoundObjectRef, but other audiences may not. Keep ExpirationSeconds small if you want prompt revocation.</TD></TR>
<TR><TD><CODE>expirationSeconds</CODE><BR /><I>integer</I></TD><TD>ExpirationSeconds is the requested duration of validity of the request. The token issuer may return a token with a different validity duration so a client needs to check the &#39;expiration&#39; field in a response.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="tokenrequeststatus-v1-authentication-k8s-io">TokenRequestStatus v1 authentication</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#tokenrequest-v1-authentication-k8s-io">TokenRequest [authentication/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expirationTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>ExpirationTimestamp is the time of expiration of the returned token.</TD></TR>
<TR><TD><CODE>token</CODE><BR /><I>string</I></TD><TD>Token is the opaque bearer token.</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
<DIV class="resource-container" id="tokenreview-v1-authentication-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">TokenReview</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></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>
<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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>audiences</CODE><BR /><I>string array</I></TD><TD>Audiences is a list of the identifiers that the resource server presented with the token identifies as. Audience-aware token authenticators will verify that the token was intended for at least one of the audiences in this list. If no audiences are provided, the audience will default to the audience of the Kubernetes apiserver.</TD></TR>
<TR><TD><CODE>token</CODE><BR /><I>string</I></TD><TD>Token is the opaque bearer token.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" 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>audiences</CODE><BR /><I>string array</I></TD><TD>Audiences are audience identifiers chosen by the authenticator that are compatible with both the TokenReview and token. An identifier is any identifier in the intersection of the TokenReviewSpec audiences and the token&#39;s audiences. A client of the TokenReview API that sets the spec.audiences field should validate that a compatible audience identifier is returned in the status.audiences field to ensure that the TokenReview server is audience aware. If a TokenReview returns an empty status.audience field where status.authenticated is &#34;true&#34;, the token is valid against the audience of the Kubernetes API server.</TD></TR>
<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>
</DIV>
<DIV class="operation-category-container" id="write-operations-tokenreview-v1-authentication-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-tokenreview-v1-authentication-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a TokenReview</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/authentication.k8s.io/v1/tokenreviews</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>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>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>
<TR><TD>202<br /><I><a href="#tokenreview-v1-authentication-k8s-io">TokenReview</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="networkpolicy-v1-networking-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">NetworkPolicy</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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-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/sig-architecture/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/sig-architecture/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/sig-architecture/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>spec represents the specification of the desired behavior for this NetworkPolicy.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>egress is a 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>ingress is a 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>podSelector 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>policyTypes is a list of rule types that the NetworkPolicy relates to. Valid options are [&#34;Ingress&#34;], [&#34;Egress&#34;], or [&#34;Ingress&#34;, &#34;Egress&#34;]. 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 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a NetworkPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>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>
<TR><TD>202<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified NetworkPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified NetworkPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>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>
</DIV>
<DIV class="operation-container" id="delete-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a NetworkPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of NetworkPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified NetworkPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind NetworkPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind NetworkPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/networkpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/networkpolicies/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/networkpolicies</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-networkpolicy-v1-networking-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of NetworkPolicy. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/networking.k8s.io/v1/watch/networkpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">MutatingAdmissionPolicy</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>MutatingAdmissionPolicy</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="#mutatingadmissionpolicylist-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyList [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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#mutatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicySpec</a></I></TD><TD>Specification of the desired behavior of the MutatingAdmissionPolicy.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="mutatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicySpec v1alpha1 admissionregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>failurePolicy</CODE><BR /><I>string</I></TD><TD>failurePolicy defines how to handle failures for the admission policy. Failures can occur from CEL expression parse errors, type check errors, runtime errors and invalid or mis-configured policy definitions or bindings. A policy is invalid if paramKind refers to a non-existent Kind. A binding is invalid if paramRef.name refers to a non-existent resource. failurePolicy does not define how validations that evaluate to false are handled. Allowed values are Ignore or Fail. Defaults to Fail.</TD></TR>
<TR><TD><CODE>matchConditions</CODE><BR /><I><a href="#matchcondition-v1alpha1-admissionregistration-k8s-io">MatchCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>matchConditions is a list of conditions that must be met for a request to be validated. Match conditions filter requests that have already been matched by the matchConstraints. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed. If a parameter object is provided, it can be accessed via the `params` handle in the same manner as validation expressions. The exact matching logic is (in order): 1. If ANY matchCondition evaluates to FALSE, the policy is skipped. 2. If ALL matchConditions evaluate to TRUE, the policy is evaluated. 3. If any matchCondition evaluates to an error (but none are FALSE): - If failurePolicy=Fail, reject the request - If failurePolicy=Ignore, the policy is skipped</TD></TR>
<TR><TD><CODE>matchConstraints</CODE><BR /><I><a href="#matchresources-v1alpha1-admissionregistration-k8s-io">MatchResources</a></I></TD><TD>matchConstraints specifies what resources this policy is designed to validate. The MutatingAdmissionPolicy cares about a request if it matches _all_ Constraints. However, in order to prevent clusters from being put into an unstable state that cannot be recovered from via the API MutatingAdmissionPolicy cannot match MutatingAdmissionPolicy and MutatingAdmissionPolicyBinding. The CREATE, UPDATE and CONNECT operations are allowed. The DELETE operation may not be matched. &#39;\*&#39; matches CREATE, UPDATE and CONNECT. Required.</TD></TR>
<TR><TD><CODE>mutations</CODE><BR /><I><a href="#mutation-v1alpha1-admissionregistration-k8s-io">Mutation</a> array</I></TD><TD>mutations contain operations to perform on matching objects. mutations may not be empty; a minimum of one mutation is required. mutations are evaluated in order, and are reinvoked according to the reinvocationPolicy. The mutations of a policy are invoked for each binding of this policy and reinvocation of mutations occurs on a per binding basis.</TD></TR>
<TR><TD><CODE>paramKind</CODE><BR /><I><a href="#paramkind-v1alpha1-admissionregistration-k8s-io">ParamKind</a></I></TD><TD>paramKind specifies the kind of resources used to parameterize this policy. If absent, there are no parameters for this policy and the param CEL variable will not be provided to validation expressions. If paramKind refers to a non-existent kind, this policy definition is mis-configured and the FailurePolicy is applied. If paramKind is specified but paramRef is unset in MutatingAdmissionPolicyBinding, the params variable will be null.</TD></TR>
<TR><TD><CODE>reinvocationPolicy</CODE><BR /><I>string</I></TD><TD>reinvocationPolicy indicates whether mutations may be called multiple times per MutatingAdmissionPolicyBinding as part of a single admission evaluation. Allowed values are &#34;Never&#34; and &#34;IfNeeded&#34;. Never: These mutations will not be called more than once per binding in a single admission evaluation. IfNeeded: These mutations may be invoked more than once per binding for a single admission request and there is no guarantee of order with respect to other admission plugins, admission webhooks, bindings of this policy and admission policies. Mutations are only reinvoked when mutations change the object after this mutation is invoked. Required.</TD></TR>
<TR><TD><CODE>variables</CODE><BR /><I><a href="#variable-v1alpha1-admissionregistration-k8s-io">Variable</a> array</I></TD><TD>variables contain definitions of variables that can be used in composition of other expressions. Each variable is defined as a named CEL expression. The variables defined here will be available under `variables` in other expressions of the policy except matchConditions because matchConditions are evaluated before the rest of the policy. The expression of a variable can refer to other variables defined earlier in the list but not those after. Thus, variables must be sorted by the order of first appearance and acyclic.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="mutatingadmissionpolicylist-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a> array</I></TD><TD>List of ValidatingAdmissionPolicy.</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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a MutatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified MutatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified MutatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a MutatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of MutatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified MutatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind MutatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingadmissionpolicylist-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind MutatingAdmissionPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/watch/mutatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of MutatingAdmissionPolicy. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/watch/mutatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">MutatingAdmissionPolicyBinding</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>MutatingAdmissionPolicyBinding</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="#mutatingadmissionpolicybindinglist-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBindingList [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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#mutatingadmissionpolicybindingspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBindingSpec</a></I></TD><TD>Specification of the desired behavior of the MutatingAdmissionPolicyBinding.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="mutatingadmissionpolicybindingspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBindingSpec v1alpha1 admissionregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>matchResources</CODE><BR /><I><a href="#matchresources-v1alpha1-admissionregistration-k8s-io">MatchResources</a></I></TD><TD>matchResources limits what resources match this binding and may be mutated by it. Note that if matchResources matches a resource, the resource must also match a policy&#39;s matchConstraints and matchConditions before the resource may be mutated. When matchResources is unset, it does not constrain resource matching, and only the policy&#39;s matchConstraints and matchConditions must match for the resource to be mutated. Additionally, matchResources.resourceRules are optional and do not constraint matching when unset. Note that this is differs from MutatingAdmissionPolicy matchConstraints, where resourceRules are required. The CREATE, UPDATE and CONNECT operations are allowed. The DELETE operation may not be matched. &#39;\*&#39; matches CREATE, UPDATE and CONNECT.</TD></TR>
<TR><TD><CODE>paramRef</CODE><BR /><I><a href="#paramref-v1alpha1-admissionregistration-k8s-io">ParamRef</a></I></TD><TD>paramRef specifies the parameter resource used to configure the admission control policy. It should point to a resource of the type specified in spec.ParamKind of the bound MutatingAdmissionPolicy. If the policy specifies a ParamKind and the resource referred to by ParamRef does not exist, this binding is considered mis-configured and the FailurePolicy of the MutatingAdmissionPolicy applied. If the policy does not specify a ParamKind then this field is ignored, and the rules are evaluated without a param.</TD></TR>
<TR><TD><CODE>policyName</CODE><BR /><I>string</I></TD><TD>policyName references a MutatingAdmissionPolicy name which the MutatingAdmissionPolicyBinding binds to. If the referenced resource does not exist, this binding is considered invalid and will be ignored Required.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="mutatingadmissionpolicybindinglist-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBindingList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a> array</I></TD><TD>List of PolicyBinding.</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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a MutatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified MutatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified MutatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a MutatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of MutatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified MutatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind MutatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/mutatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingadmissionpolicybindinglist-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind MutatingAdmissionPolicyBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/watch/mutatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of MutatingAdmissionPolicyBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/watch/mutatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV id="definitions">
<H1 class="toc-item section">Definitions</H1>
<P>This section contains definitions for objects used in the Kubernetes APIs.</P>
</DIV>
<DIV class="definition-container" id="apigroup-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">APIGroup</span> <span class="v">v1</span> <span class="g">meta</span></span></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/sig-architecture/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/sig-architecture/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>
</DIV>
<DIV class="definition-container" id="apiresource-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">APIResource</span> <span class="v">v1</span> <span class="g">meta</span></span></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>storageVersionHash</CODE><BR /><I>string</I></TD><TD>The hash value of the storage version, the version this resource is converted to when written to the data store. Value must be treated as opaque by clients. Only equality comparison on the value is valid. This is an alpha feature and may change or be removed in the future. The field is populated by the apiserver only if the StorageVersionHash feature gate is enabled. This field will remain optional even if it graduates.</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>
</DIV>
<DIV class="definition-container" id="apiservicecondition-v1-apiregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">APIServiceCondition</span> <span class="v">v1</span> <span class="g">apiregistration.k8s.io</span></span></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>APIServiceCondition describes the state of an APIService at a particular point</P>
<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>
</DIV>
<DIV class="definition-container" id="apiversions-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">APIVersions</span> <span class="v">v1</span> <span class="g">meta</span></span></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/sig-architecture/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/sig-architecture/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>
</DIV>
<DIV class="definition-container" id="awselasticblockstorevolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">AWSElasticBlockStoreVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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>partition is 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>readOnly value true will force the readOnly setting in VolumeMounts. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>volumeID is 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>
</DIV>
<DIV class="definition-container" id="affinity-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">Affinity</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="aggregationrule-v1-rbac-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">AggregationRule</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></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-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>
</DIV>
<DIV class="definition-container" id="allocateddevicestatus-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">AllocatedDeviceStatus</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AllocatedDeviceStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AllocatedDeviceStatus contains the status of an allocated device, if the driver chooses to report it. This may include driver-specific information.</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="#allocateddevicestatus-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaimstatus-v1beta1-resource-k8s-io">ResourceClaimStatus [resource/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="#condition-v1-meta">Condition</a> array</I></TD><TD>Conditions contains the latest observation of the device&#39;s state. If the device has been configured according to the class and claim config references, the `Ready` condition should be True.</TD></TR>
<TR><TD><CODE>data</CODE></TD><TD>Data contains arbitrary driver-specific data. The length of the raw data must be smaller or equal to 10 Ki.</TD></TR>
<TR><TD><CODE>device</CODE><BR /><I>string</I></TD><TD>Device references one device instance via its name in the driver&#39;s resource pool. It must be a DNS label.</TD></TR>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver specifies the name of the DRA driver whose kubelet plugin should be invoked to process the allocation once the claim is needed on a node. Must be a DNS subdomain and should end with a DNS domain owned by the vendor of the driver.</TD></TR>
<TR><TD><CODE>networkData</CODE><BR /><I><a href="#networkdevicedata-v1beta1-resource-k8s-io">NetworkDeviceData</a></I></TD><TD>NetworkData contains network-related information specific to the device.</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>This name together with the driver name and the device name field identify which device was allocated (`&lt;driver name&gt;/&lt;pool name&gt;/&lt;device name&gt;`). Must not be longer than 253 characters and may contain one or more DNS sub-domains separated by slashes.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="allocationresult-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">AllocationResult</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AllocationResult</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AllocationResult contains attributes of an allocated 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="#allocationresult-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaimstatus-v1beta1-resource-k8s-io">ResourceClaimStatus [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#deviceallocationresult-v1beta1-resource-k8s-io">DeviceAllocationResult</a></I></TD><TD>Devices is the result of allocating devices.</TD></TR>
<TR><TD><CODE>nodeSelector</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>NodeSelector defines where the allocated resources are available. If unset, they are available everywhere.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="apparmorprofile-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">AppArmorProfile</span> <span class="v">v1</span> <span class="g">core</span></span></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>AppArmorProfile</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AppArmorProfile defines a pod or container&#39;s AppArmor settings.</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="#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>localhostProfile</CODE><BR /><I>string</I></TD><TD>localhostProfile indicates a profile loaded on the node that should be used. The profile must be preconfigured on the node to work. Must match the loaded name of the profile. Must be set if and only if type is &#34;Localhost&#34;.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type indicates which kind of AppArmor profile will be applied. Valid options are: Localhost - a profile pre-loaded on the node. RuntimeDefault - the container runtime&#39;s default profile. Unconfined - no AppArmor enforcement.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="applyconfiguration-v1alpha1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ApplyConfiguration</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>ApplyConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ApplyConfiguration defines the desired configuration values 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="#mutation-v1alpha1-admissionregistration-k8s-io">Mutation [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>expression will be evaluated by CEL to create an apply configuration. ref: https://github.com/google/cel-spec Apply configurations are declared in CEL using object initialization. For example, this CEL expression returns an apply configuration to set a single field: Object{ spec: Object.spec{ serviceAccountName: &#34;example&#34; } } Apply configurations may not modify atomic structs, maps or arrays due to the risk of accidental deletion of values not included in the apply configuration. CEL expressions have access to the object types needed to create apply configurations: - &#39;Object&#39; - CEL type of the resource object. - &#39;Object.&lt;fieldName&gt;&#39; - CEL type of object field (such as &#39;Object.spec&#39;) - &#39;Object.&lt;fieldName1&gt;.&lt;fieldName2&gt;...&lt;fieldNameN&gt;` - CEL type of nested field (such as &#39;Object.spec.containers&#39;) CEL expressions have access to the contents of the API request, organized into CEL variables as well as some other useful variables: - &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. - &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. - &#39;request&#39; - Attributes of the API request([ref](/pkg/apis/admission/types.go#AdmissionRequest)). - &#39;params&#39; - Parameter resource referred to by the policy binding being evaluated. Only populated if the policy has a ParamKind. - &#39;namespaceObject&#39; - The namespace object that the incoming object belongs to. The value is null for cluster-scoped resources. - &#39;variables&#39; - Map of composited variables, from its name to its lazily evaluated value. For example, a variable named &#39;foo&#39; can be accessed as &#39;variables.foo&#39;. - &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request. See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz - &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the request resource. The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object. No other metadata properties are accessible. Only property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="attachedvolume-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">AttachedVolume</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="auditannotation-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">AuditAnnotation</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>AuditAnnotation</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AuditAnnotation describes how to produce an audit annotation for an API request.</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="#auditannotation-v1beta1-admissionregistration-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="#validatingadmissionpolicyspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/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>key specifies the audit annotation key. The audit annotation keys of a ValidatingAdmissionPolicy must be unique. The key must be a qualified name ([A-Za-z0-9][-A-Za-z0-9_.]*) no more than 63 bytes in length. The key is combined with the resource name of the ValidatingAdmissionPolicy to construct an audit annotation key: &#34;{ValidatingAdmissionPolicy name}/{key}&#34;. If an admission webhook uses the same resource name as this ValidatingAdmissionPolicy and the same audit annotation key, the annotation key will be identical. In this case, the first annotation written with the key will be included in the audit event and all subsequent annotations with the same key will be discarded. Required.</TD></TR>
<TR><TD><CODE>valueExpression</CODE><BR /><I>string</I></TD><TD>valueExpression represents the expression which is evaluated by CEL to produce an audit annotation value. The expression must evaluate to either a string or null value. If the expression evaluates to a string, the audit annotation is included with the string value. If the expression evaluates to null or empty string the audit annotation will be omitted. The valueExpression may be no longer than 5kb in length. If the result of the valueExpression is more than 10kb in length, it will be truncated to 10kb. If multiple ValidatingAdmissionPolicyBinding resources match an API request, then the valueExpression will be evaluated for each binding. All unique values produced by the valueExpressions will be joined together in a comma-separated list. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="azurediskvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">AzureDiskVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>cachingMode is the Host Caching mode: None, Read Only, Read Write.</TD></TR>
<TR><TD><CODE>diskName</CODE><BR /><I>string</I></TD><TD>diskName is the Name of the data disk in the blob storage</TD></TR>
<TR><TD><CODE>diskURI</CODE><BR /><I>string</I></TD><TD>diskURI is the URI of data disk in the blob storage</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>fsType is 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>kind expected values are 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>readOnly Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="azurefilepersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">AzureFilePersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>readOnly 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>secretName is 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>secretNamespace is 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>shareName is the azure Share Name</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="azurefilevolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">AzureFileVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>readOnly 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>secretName is 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>shareName is the azure share Name</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="basicdevice-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">BasicDevice</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>BasicDevice</CODE></TD></TR>
</TBODY>
</TABLE>
<P>BasicDevice defines one device instance.</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="#basicdevice-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#device-v1beta1-resource-k8s-io">Device [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>attributes</CODE><BR /><I>object</I></TD><TD>Attributes defines the set of attributes for this device. The name of each attribute must be unique in that set. The maximum number of attributes and capacities combined is 32.</TD></TR>
<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>Capacity defines the set of capacities for this device. The name of each capacity must be unique in that set. The maximum number of attributes and capacities combined is 32.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="boundobjectreference-v1-authentication-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">BoundObjectReference</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></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>BoundObjectReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>BoundObjectReference is a reference to an object that a token is bound to.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#tokenrequestspec-v1-authentication-k8s-io">TokenRequestSpec [authentication/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. Valid kinds are &#39;Pod&#39; and &#39;Secret&#39;.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent.</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID of the referent.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="celdeviceselector-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CELDeviceSelector</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CELDeviceSelector</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CELDeviceSelector contains a CEL expression for selecting a device.</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="#celdeviceselector-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceselector-v1beta1-resource-k8s-io">DeviceSelector [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression is a CEL expression which evaluates a single device. It must evaluate to true when the device under consideration satisfies the desired criteria, and false when it does not. Any other result is an error and causes allocation of devices to abort. The expression&#39;s input is an object named &#34;device&#34;, which carries the following properties: - driver (string): the name of the driver which defines this device. - attributes (map[string]object): the device&#39;s attributes, grouped by prefix (e.g. device.attributes[&#34;dra.example.com&#34;] evaluates to an object with all of the attributes which were prefixed by &#34;dra.example.com&#34;. - capacity (map[string]object): the device&#39;s capacities, grouped by prefix. Example: Consider a device with driver=&#34;dra.example.com&#34;, which exposes two attributes named &#34;model&#34; and &#34;ext.example.com/family&#34; and which exposes one capacity named &#34;modules&#34;. This input to this expression would have the following fields: device.driver device.attributes[&#34;dra.example.com&#34;].model device.attributes[&#34;ext.example.com&#34;].family device.capacity[&#34;dra.example.com&#34;].modules The device.driver field can be used to check for a specific driver, either as a high-level precondition (i.e. you only want to consider devices from this driver) or as part of a multi-clause expression that is meant to consider devices from different drivers. The value type of each attribute is defined by the device definition, and users who write these expressions must consult the documentation for their specific drivers. The value type of each capacity is Quantity. If an unknown prefix is used as a lookup in either device.attributes or device.capacity, an empty map will be returned. Any reference to an unknown field will cause an evaluation error and allocation to abort. A robust expression should check for the existence of attributes before referencing them. For ease of use, the cel.bind() function is enabled, and can be used to simplify expressions that access multiple attributes with the same domain. For example: cel.bind(dra, device.attributes[&#34;dra.example.com&#34;], dra.someBool &amp;&amp; dra.anotherBool) The length of the expression must be smaller or equal to 10 Ki. The cost of evaluating it is also limited based on the estimated number of logical steps.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="csinodedriver-v1-storage-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CSINodeDriver</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>CSINodeDriver</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CSINodeDriver holds information about the specification of one CSI driver installed on a node</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#csinodespec-v1-storage-k8s-io">CSINodeSpec [storage/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allocatable</CODE><BR /><I><a href="#volumenoderesources-v1-storage-k8s-io">VolumeNodeResources</a></I></TD><TD>allocatable represents the volume resources of a node that are available for scheduling. This field is beta.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name represents the name of the CSI driver that this object refers to. This MUST be the same name returned by the CSI GetPluginName() call for that driver.</TD></TR>
<TR><TD><CODE>nodeID</CODE><BR /><I>string</I></TD><TD>nodeID of the node from the driver point of view. This field enables Kubernetes to communicate with storage systems that do not share the same nomenclature for nodes. For example, Kubernetes may refer to a given node as &#34;node1&#34;, but the storage system may refer to the same node as &#34;nodeA&#34;. When Kubernetes issues a command to the storage system to attach a volume to a specific node, it can use this field to refer to the node name using the ID that the storage system will understand, e.g. &#34;nodeA&#34; instead of &#34;node1&#34;. This field is required.</TD></TR>
<TR><TD><CODE>topologyKeys</CODE><BR /><I>string array</I></TD><TD>topologyKeys is the list of keys supported by the driver. When a driver is initialized on a cluster, it provides a set of topology keys that it understands (e.g. &#34;company.com/zone&#34;, &#34;company.com/region&#34;). When a driver is initialized on a node, it provides the same topology keys along with values. Kubelet will expose these topology keys as labels on its own node object. When Kubernetes does topology aware provisioning, it can use this list to determine which labels it should retrieve from the node object and pass back to the driver. It is possible for different nodes to use different topology keys. This can be empty if driver does not support topology.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="csipersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">CSIPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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</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>controllerExpandSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>controllerExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerExpandVolume call. 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>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>fsType to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;.</TD></TR>
<TR><TD><CODE>nodeExpandSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>nodeExpandSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeExpandVolume call. This field is optional, may be omitted if no secret is required. If the secret object contains more than one secret, all secrets are passed.</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>readOnly value to pass to ControllerPublishVolumeRequest. Defaults to false (read/write).</TD></TR>
<TR><TD><CODE>volumeAttributes</CODE><BR /><I>object</I></TD><TD>volumeAttributes 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 plugins CreateVolume to refer to the volume on all subsequent calls. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="csivolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">CSIVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>CSIVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a source location of a volume to mount, managed by an external CSI driver</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 CSI driver that handles this volume. Consult with your admin for the correct name as registered in the cluster.</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>fsType to mount. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. If not provided, the empty value is passed to the associated CSI driver which will determine the default filesystem to apply.</TD></TR>
<TR><TD><CODE>nodePublishSecretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</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 secret references are passed.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly specifies a read-only configuration for the volume. Defaults to false (read/write).</TD></TR>
<TR><TD><CODE>volumeAttributes</CODE><BR /><I>object</I></TD><TD>volumeAttributes stores driver-specific properties that are passed to the CSI driver. Consult your driver&#39;s documentation for supported values.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="capabilities-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">Capabilities</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="cephfspersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">CephFSPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>monitors is Required: Monitors is a collection of Ceph monitors More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>path is 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>readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>secretFile</CODE><BR /><I>string</I></TD><TD>secretFile is Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://examples.k8s.io/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>secretRef is Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>user is Optional: User is the rados user name, default is admin More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="cephfsvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">CephFSVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>monitors is Required: Monitors is a collection of Ceph monitors More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>path is 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>readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>secretFile</CODE><BR /><I>string</I></TD><TD>secretFile is Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://examples.k8s.io/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>secretRef is Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>user is optional: User is the rados user name, default is admin More info: https://examples.k8s.io/volumes/cephfs/README.md#how-to-use-it</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="certificatesigningrequestcondition-v1-certificates-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CertificateSigningRequestCondition</span> <span class="v">v1</span> <span class="g">certificates.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>CertificateSigningRequestCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CertificateSigningRequestCondition describes a condition of a CertificateSigningRequest object</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#certificatesigningrequeststatus-v1-certificates-k8s-io">CertificateSigningRequestStatus [certificates/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>lastTransitionTime is the time the condition last transitioned from one status to another. If unset, when a new condition type is added or an existing condition&#39;s status is changed, the server defaults this to the current time.</TD></TR>
<TR><TD><CODE>lastUpdateTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastUpdateTime is the time of the last update to this condition</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message contains a human readable message with details about the request state</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason indicates a brief reason for the request state</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>status of the condition, one of True, False, Unknown. Approved, Denied, and Failed conditions may not be &#34;False&#34; or &#34;Unknown&#34;.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type of the condition. Known conditions are &#34;Approved&#34;, &#34;Denied&#34;, and &#34;Failed&#34;. An &#34;Approved&#34; condition is added via the /approval subresource, indicating the request was approved and should be issued by the signer. A &#34;Denied&#34; condition is added via the /approval subresource, indicating the request was denied and should not be issued by the signer. A &#34;Failed&#34; condition is added via the /status subresource, indicating the signer failed to issue the certificate. Approved and Denied conditions are mutually exclusive. Approved, Denied, and Failed conditions cannot be removed once added. Only one condition of a given type is allowed.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="cinderpersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">CinderPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType 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://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly is Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>secretRef is 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>volumeID used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="cindervolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">CinderVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>secretRef is 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>volumeID used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="clientipconfig-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ClientIPConfig</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="clustertrustbundleprojection-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ClusterTrustBundleProjection</span> <span class="v">v1</span> <span class="g">core</span></span></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>ClusterTrustBundleProjection</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ClusterTrustBundleProjection describes how to select a set of ClusterTrustBundle objects and project their contents into the pod filesystem.</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>labelSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Select all ClusterTrustBundles that match this label selector. Only has effect if signerName is set. Mutually-exclusive with name. If unset, interpreted as &#34;match nothing&#34;. If set but empty, interpreted as &#34;match everything&#34;.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Select a single ClusterTrustBundle by object name. Mutually-exclusive with signerName and labelSelector.</TD></TR>
<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>If true, don&#39;t block pod startup if the referenced ClusterTrustBundle(s) aren&#39;t available. If using name, then the named ClusterTrustBundle is allowed not to exist. If using signerName, then the combination of signerName and labelSelector is allowed to match zero ClusterTrustBundles.</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Relative path from the volume root to write the bundle.</TD></TR>
<TR><TD><CODE>signerName</CODE><BR /><I>string</I></TD><TD>Select all ClusterTrustBundles that match this signer name. Mutually-exclusive with name. The contents of all selected ClusterTrustBundles will be unified and deduplicated.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="componentcondition-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ComponentCondition</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="condition-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">Condition</span> <span class="v">v1</span> <span class="g">meta</span></span></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>Condition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Condition contains details for one aspect of the current state of this API Resource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#allocateddevicestatus-v1beta1-resource-k8s-io">AllocatedDeviceStatus [resource/v1beta1]</a></LI>
<LI><a href="#allocateddevicestatus-v1alpha3-resource-k8s-io">AllocatedDeviceStatus [resource/v1alpha3]</a></LI>
<LI><a href="#poddisruptionbudgetstatus-v1-policy">PodDisruptionBudgetStatus [policy/v1]</a></LI>
<LI><a href="#servicecidrstatus-v1beta1-networking-k8s-io">ServiceCIDRStatus [networking/v1beta1]</a></LI>
<LI><a href="#servicestatus-v1-core">ServiceStatus [core/v1]</a></LI>
<LI><a href="#validatingadmissionpolicystatus-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus [admissionregistration/v1]</a></LI>
<LI><a href="#validatingadmissionpolicystatus-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus [admissionregistration/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>lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is a human readable message indicating details about the transition. This may be an empty string.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason contains a programmatic identifier indicating the reason for the condition&#39;s last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty.</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 condition in CamelCase or in foo.example.com/CamelCase.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="configmapenvsource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ConfigMapEnvSource</span> <span class="v">v1</span> <span class="g">core</span></span></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. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. 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>
</DIV>
<DIV class="definition-container" id="configmapkeyselector-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ConfigMapKeySelector</span> <span class="v">v1</span> <span class="g">core</span></span></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. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. 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 its key must be defined</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="configmapnodeconfigsource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ConfigMapNodeConfigSource</span> <span class="v">v1</span> <span class="g">core</span></span></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. This API is deprecated since 1.22: https://git.k8s.io/enhancements/keps/sig-node/281-dynamic-kubelet-configuration</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>
</DIV>
<DIV class="definition-container" id="configmapprojection-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ConfigMapProjection</span> <span class="v">v1</span> <span class="g">core</span></span></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>items 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. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. 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>optional specify whether the ConfigMap or its keys must be defined</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="configmapvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ConfigMapVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>defaultMode is optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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>items 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. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. 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>optional specify whether the ConfigMap or its keys must be defined</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="containerimage-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ContainerImage</span> <span class="v">v1</span> <span class="g">core</span></span></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;kubernetes.example/hyperkube:v1.0.7&#34;, &#34;cloud-vendor.registry.example/cloud-vendor/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>
</DIV>
<DIV class="definition-container" id="containerport-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ContainerPort</span> <span class="v">v1</span> <span class="g">core</span></span></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>
<LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [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, TCP, or SCTP. Defaults to &#34;TCP&#34;.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="containerresizepolicy-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ContainerResizePolicy</span> <span class="v">v1</span> <span class="g">core</span></span></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>ContainerResizePolicy</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ContainerResizePolicy represents resource resize policy for the 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="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resourceName</CODE><BR /><I>string</I></TD><TD>Name of the resource to which this resource resize policy applies. Supported values: cpu, memory.</TD></TR>
<TR><TD><CODE>restartPolicy</CODE><BR /><I>string</I></TD><TD>Restart policy to apply when specified resource is resized. If not specified, it defaults to NotRequired.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="containerresourcemetricsource-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">ContainerResourceMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</CODE></TD><TD><CODE>ContainerResourceMetricSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ContainerResourceMetricSource 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-v2-autoscaling">MetricSpec [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>container</CODE><BR /><I>string</I></TD><TD>container is the name of the container in the pods of the scaling target</TD></TR>
<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>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="containerresourcemetricstatus-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">ContainerResourceMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</CODE></TD><TD><CODE>ContainerResourceMetricStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ContainerResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing a single container in 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-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>container</CODE><BR /><I>string</I></TD><TD>container is the name of the container in the pods of the scaling target</TD></TR>
<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</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>
</DIV>
<DIV class="definition-container" id="containerstate-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ContainerState</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="containerstaterunning-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ContainerStateRunning</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="containerstateterminated-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ContainerStateTerminated</span> <span class="v">v1</span> <span class="g">core</span></span></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;&lt;type&gt;://&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>
</DIV>
<DIV class="definition-container" id="containerstatewaiting-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ContainerStateWaiting</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="containeruser-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ContainerUser</span> <span class="v">v1</span> <span class="g">core</span></span></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>ContainerUser</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ContainerUser represents user identity information</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>linux</CODE><BR /><I><a href="#linuxcontaineruser-v1-core">LinuxContainerUser</a></I></TD><TD>Linux holds user identity information initially attached to the first process of the containers in Linux. Note that the actual running identity can be changed if the process has enough privilege to do so.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="crossversionobjectreference-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">CrossVersionObjectReference</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-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-v2-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2]</a></LI>
<LI><a href="#objectmetricsource-v2-autoscaling">ObjectMetricSource [autoscaling/v2]</a></LI>
<LI><a href="#objectmetricstatus-v2-autoscaling">ObjectMetricStatus [autoscaling/v2]</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 is the API version of the referent</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>kind is the kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="customresourcecolumndefinition-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CustomResourceColumnDefinition</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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="#customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion [apiextensions/v1]</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>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 details.</TD></TR>
<TR><TD><CODE>jsonPath</CODE><BR /><I>string</I></TD><TD>jsonPath is a simple JSON path (i.e. with array notation) which is evaluated against each custom resource to produce the value for this column.</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 priority greater than 0.</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 details.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="customresourceconversion-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CustomResourceConversion</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>CustomResourceConversion</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CustomResourceConversion describes how to convert different versions of a CR.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionspec-v1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>strategy</CODE><BR /><I>string</I></TD><TD>strategy specifies how custom resources are converted between versions. Allowed values are: - `&#34;None&#34;`: The converter only change the apiVersion and would not touch any other field in the custom resource. - `&#34;Webhook&#34;`: API Server will call to an external webhook to do the conversion. Additional information is needed for this option. This requires spec.preserveUnknownFields to be false, and spec.conversion.webhook to be set.</TD></TR>
<TR><TD><CODE>webhook</CODE><BR /><I><a href="#webhookconversion-v1-apiextensions-k8s-io">WebhookConversion</a></I></TD><TD>webhook describes how to call the conversion webhook. Required when `strategy` is set to `&#34;Webhook&#34;`.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="customresourcedefinitioncondition-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CustomResourceDefinitionCondition</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">CustomResourceDefinitionStatus [apiextensions/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>lastTransitionTime 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 message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason is a 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. Types include Established, NamesAccepted and Terminating.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="customresourcedefinitionnames-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CustomResourceDefinitionNames</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1]</a></LI>
<LI><a href="#customresourcedefinitionstatus-v1-apiextensions-k8s-io">CustomResourceDefinitionStatus [apiextensions/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 grouped resources this custom resource belongs to (e.g. &#39;all&#39;). This is published in API discovery documents, and used by clients to support invocations like `kubectl get all`.</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. Custom resource instances will use this value as the `kind` attribute in API calls.</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 &#34;`kind`List&#34;.</TD></TR>
<TR><TD><CODE>plural</CODE><BR /><I>string</I></TD><TD>plural is the plural name of the resource to serve. The custom resources are served under `/apis/&lt;group&gt;/&lt;version&gt;/.../&lt;plural&gt;`. Must match the name of the CustomResourceDefinition (in the form `&lt;names.plural&gt;.&lt;group&gt;`). 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, exposed in API discovery documents, and used by clients to support invocations like `kubectl get &lt;shortname&gt;`. 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 `kind`.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="customresourcedefinitionversion-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CustomResourceDefinitionVersion</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>CustomResourceDefinitionVersion</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CustomResourceDefinitionVersion describes a version for CRD.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionspec-v1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1]</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-v1-apiextensions-k8s-io">CustomResourceColumnDefinition</a> array</I></TD><TD>additionalPrinterColumns specifies additional columns returned in Table output. See https://kubernetes.io/docs/reference/using-api/api-concepts/#receiving-resources-as-tables for details. If no columns are specified, a single column displaying the age of the custom resource is used.</TD></TR>
<TR><TD><CODE>deprecated</CODE><BR /><I>boolean</I></TD><TD>deprecated indicates this version of the custom resource API is deprecated. When set to true, API requests to this version receive a warning header in the server response. Defaults to false.</TD></TR>
<TR><TD><CODE>deprecationWarning</CODE><BR /><I>string</I></TD><TD>deprecationWarning overrides the default warning returned to API clients. May only be set when `deprecated` is true. The default warning indicates this version is deprecated and recommends use of the newest served version of equal or greater stability, if one exists.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the version name, e.g. “v1”, “v2beta1”, etc. The custom resources are served under this version at `/apis/&lt;group&gt;/&lt;version&gt;/...` if `served` is true.</TD></TR>
<TR><TD><CODE>schema</CODE><BR /><I><a href="#customresourcevalidation-v1-apiextensions-k8s-io">CustomResourceValidation</a></I></TD><TD>schema describes the schema used for validation, pruning, and defaulting of this version of the custom resource.</TD></TR>
<TR><TD><CODE>selectableFields</CODE><BR /><I><a href="#selectablefield-v1-apiextensions-k8s-io">SelectableField</a> array</I></TD><TD>selectableFields specifies paths to fields that may be used as field selectors. A maximum of 8 selectable fields are allowed. See https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors</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 indicates this version should be used when persisting custom resources to storage. There must be exactly one version with storage=true.</TD></TR>
<TR><TD><CODE>subresources</CODE><BR /><I><a href="#customresourcesubresources-v1-apiextensions-k8s-io">CustomResourceSubresources</a></I></TD><TD>subresources specify what subresources this version of the defined custom resource have.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="customresourcesubresourcescale-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CustomResourceSubresourceScale</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">CustomResourceSubresources [apiextensions/v1]</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 custom resource that corresponds to Scale `status.selector`. Only JSON paths without the array notation are allowed. Must be a JSON Path under `.status` or `.spec`. Must be set to work with HorizontalPodAutoscaler. The field pointed by this JSON path must be a string field (not a complex selector struct) which contains a serialized label selector in string form. More info: https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions#scale-subresource If there is no value under the given path in the custom resource, the `status.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 custom resource 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 custom resource, 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 custom resource 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 custom resource, the `status.replicas` value in the `/scale` subresource will default to 0.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="customresourcesubresourcestatus-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CustomResourceSubresourceStatus</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">CustomResourceSubresources [apiextensions/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="customresourcesubresources-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CustomResourceSubresources</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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="#customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion [apiextensions/v1]</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-v1-apiextensions-k8s-io">CustomResourceSubresourceScale</a></I></TD><TD>scale indicates the custom resource should serve a `/scale` subresource that returns an `autoscaling/v1` Scale object.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#customresourcesubresourcestatus-v1-apiextensions-k8s-io">CustomResourceSubresourceStatus</a></I></TD><TD>status indicates the custom resource should serve a `/status` subresource. When enabled: 1. requests to the custom resource primary endpoint ignore changes to the `status` stanza of the object. 2. requests to the custom resource `/status` subresource ignore changes to anything other than the `status` stanza of the object.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="customresourcevalidation-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">CustomResourceValidation</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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="#customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion [apiextensions/v1]</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-v1-apiextensions-k8s-io">JSONSchemaProps</a></I></TD><TD>openAPIV3Schema is the OpenAPI v3 schema to use for validation and pruning.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="daemonendpoint-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">DaemonEndpoint</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="daemonsetcondition-v1-apps">
<H2 class="definition"><span class="gvk"><span class="k">DaemonSetCondition</span> <span class="v">v1</span> <span class="g">apps</span></span></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-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>
</DIV>
<DIV class="definition-container" id="daemonsetupdatestrategy-v1-apps">
<H2 class="definition"><span class="gvk"><span class="k">DaemonSetUpdateStrategy</span> <span class="v">v1</span> <span class="g">apps</span></span></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-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>
</DIV>
<DIV class="definition-container" id="deleteoptions-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">DeleteOptions</span> <span class="v">v1</span> <span class="g">meta</span></span></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-v1-policy">Eviction [policy/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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>dryRun</CODE><BR /><I>string array</I></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE><BR /><I>boolean</I></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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/sig-architecture/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>
</DIV>
<DIV class="definition-container" id="deploymentcondition-v1-apps">
<H2 class="definition"><span class="gvk"><span class="k">DeploymentCondition</span> <span class="v">v1</span> <span class="g">apps</span></span></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-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>
</DIV>
<DIV class="definition-container" id="device-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">Device</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Device</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Device represents one individual hardware instance that can be selected based on its attributes. Besides the name, exactly one field must 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="#device-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceslicespec-v1beta1-resource-k8s-io">ResourceSliceSpec [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>basic</CODE><BR /><I><a href="#basicdevice-v1beta1-resource-k8s-io">BasicDevice</a></I></TD><TD>Basic defines one device instance.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is unique identifier among all devices managed by the driver in the pool. It must be a DNS label.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="deviceallocationconfiguration-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceAllocationConfiguration</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceAllocationConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceAllocationConfiguration gets embedded in an AllocationResult.</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="#deviceallocationconfiguration-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceallocationresult-v1beta1-resource-k8s-io">DeviceAllocationResult [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>opaque</CODE><BR /><I><a href="#opaquedeviceconfiguration-v1beta1-resource-k8s-io">OpaqueDeviceConfiguration</a></I></TD><TD>Opaque provides driver-specific configuration parameters.</TD></TR>
<TR><TD><CODE>requests</CODE><BR /><I>string array</I></TD><TD>Requests lists the names of requests where the configuration applies. If empty, its applies to all requests.</TD></TR>
<TR><TD><CODE>source</CODE><BR /><I>string</I></TD><TD>Source records whether the configuration comes from a class and thus is not something that a normal user would have been able to set or from a claim.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="deviceallocationresult-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceAllocationResult</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceAllocationResult</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceAllocationResult is the result of allocating devices.</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="#deviceallocationresult-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#allocationresult-v1beta1-resource-k8s-io">AllocationResult [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>config</CODE><BR /><I><a href="#deviceallocationconfiguration-v1beta1-resource-k8s-io">DeviceAllocationConfiguration</a> array</I></TD><TD>This field is a combination of all the claim and class configuration parameters. Drivers can distinguish between those based on a flag. This includes configuration parameters for drivers which have no allocated devices in the result because it is up to the drivers which configuration parameters they support. They can silently ignore unknown configuration parameters.</TD></TR>
<TR><TD><CODE>results</CODE><BR /><I><a href="#devicerequestallocationresult-v1beta1-resource-k8s-io">DeviceRequestAllocationResult</a> array</I></TD><TD>Results lists all allocated devices.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="deviceattribute-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceAttribute</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceAttribute</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceAttribute must have exactly one field 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="#deviceattribute-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#basicdevice-v1beta1-resource-k8s-io">BasicDevice [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>bool</CODE><BR /><I>boolean</I></TD><TD>BoolValue is a true/false value.</TD></TR>
<TR><TD><CODE>int</CODE><BR /><I>integer</I></TD><TD>IntValue is a number.</TD></TR>
<TR><TD><CODE>string</CODE><BR /><I>string</I></TD><TD>StringValue is a string. Must not be longer than 64 characters.</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>VersionValue is a semantic version according to semver.org spec 2.0.0. Must not be longer than 64 characters.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="devicecapacity-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceCapacity</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceCapacity</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceCapacity describes a quantity associated with a device.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#basicdevice-v1beta1-resource-k8s-io">BasicDevice [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>value</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>Value defines how much of a certain device capacity is available.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="deviceclaim-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceClaim</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceClaim</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceClaim defines how to request devices with a ResourceClaim.</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="#deviceclaim-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaimspec-v1beta1-resource-k8s-io">ResourceClaimSpec [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>config</CODE><BR /><I><a href="#deviceclaimconfiguration-v1beta1-resource-k8s-io">DeviceClaimConfiguration</a> array</I></TD><TD>This field holds configuration for multiple potential drivers which could satisfy requests in this claim. It is ignored while allocating the claim.</TD></TR>
<TR><TD><CODE>constraints</CODE><BR /><I><a href="#deviceconstraint-v1beta1-resource-k8s-io">DeviceConstraint</a> array</I></TD><TD>These constraints must be satisfied by the set of devices that get allocated for the claim.</TD></TR>
<TR><TD><CODE>requests</CODE><BR /><I><a href="#devicerequest-v1beta1-resource-k8s-io">DeviceRequest</a> array</I></TD><TD>Requests represent individual requests for distinct devices which must all be satisfied. If empty, nothing needs to be allocated.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="deviceclaimconfiguration-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceClaimConfiguration</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceClaimConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceClaimConfiguration is used for configuration parameters in DeviceClaim.</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="#deviceclaimconfiguration-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceclaim-v1beta1-resource-k8s-io">DeviceClaim [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>opaque</CODE><BR /><I><a href="#opaquedeviceconfiguration-v1beta1-resource-k8s-io">OpaqueDeviceConfiguration</a></I></TD><TD>Opaque provides driver-specific configuration parameters.</TD></TR>
<TR><TD><CODE>requests</CODE><BR /><I>string array</I></TD><TD>Requests lists the names of requests where the configuration applies. If empty, it applies to all requests.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="deviceclassconfiguration-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceClassConfiguration</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceClassConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceClassConfiguration is used in DeviceClass.</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="#deviceclassconfiguration-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceclassspec-v1beta1-resource-k8s-io">DeviceClassSpec [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>opaque</CODE><BR /><I><a href="#opaquedeviceconfiguration-v1beta1-resource-k8s-io">OpaqueDeviceConfiguration</a></I></TD><TD>Opaque provides driver-specific configuration parameters.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="deviceconstraint-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceConstraint</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceConstraint</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceConstraint must have exactly one field set besides Requests.</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="#deviceconstraint-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceclaim-v1beta1-resource-k8s-io">DeviceClaim [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>matchAttribute</CODE><BR /><I>string</I></TD><TD>MatchAttribute requires that all devices in question have this attribute and that its type and value are the same across those devices. For example, if you specified &#34;dra.example.com/numa&#34; (a hypothetical example!), then only devices in the same NUMA node will be chosen. A device which does not have that attribute will not be chosen. All devices should use a value of the same type for this attribute because that is part of its specification, but if one device doesn&#39;t, then it also will not be chosen. Must include the domain qualifier.</TD></TR>
<TR><TD><CODE>requests</CODE><BR /><I>string array</I></TD><TD>Requests is a list of the one or more requests in this claim which must co-satisfy this constraint. If a request is fulfilled by multiple devices, then all of the devices must satisfy the constraint. If this is not specified, this constraint applies to all requests in this claim.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="devicerequest-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceRequest</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceRequest</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceRequest is a request for devices required for a claim. This is typically a request for a single resource like a device, but can also ask for several identical devices.
A DeviceClassName is currently required. Clients must check that it is indeed set. It&#39;s absence indicates that something changed in a way that is not supported by the client yet, in which case it must refuse to handle the request.</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="#devicerequest-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceclaim-v1beta1-resource-k8s-io">DeviceClaim [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>adminAccess</CODE><BR /><I>boolean</I></TD><TD>AdminAccess indicates that this is a claim for administrative access to the device(s). Claims with AdminAccess are expected to be used for monitoring or other management services for a device. They ignore all ordinary claims to the device with respect to access modes and any resource allocations. This is an alpha field and requires enabling the DRAAdminAccess feature gate. Admin access is disabled if this field is unset or set to false, otherwise it is enabled.</TD></TR>
<TR><TD><CODE>allocationMode</CODE><BR /><I>string</I></TD><TD>AllocationMode and its related fields define how devices are allocated to satisfy this request. Supported values are: - ExactCount: This request is for a specific number of devices. This is the default. The exact number is provided in the count field. - All: This request is for all of the matching devices in a pool. Allocation will fail if some devices are already allocated, unless adminAccess is requested. If AlloctionMode is not specified, the default mode is ExactCount. If the mode is ExactCount and count is not specified, the default count is one. Any other requests must specify this field. More modes may get added in the future. Clients must refuse to handle requests with unknown modes.</TD></TR>
<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>Count is used only when the count mode is &#34;ExactCount&#34;. Must be greater than zero. If AllocationMode is ExactCount and this field is not specified, the default is one.</TD></TR>
<TR><TD><CODE>deviceClassName</CODE><BR /><I>string</I></TD><TD>DeviceClassName references a specific DeviceClass, which can define additional configuration and selectors to be inherited by this request. A class is required. Which classes are available depends on the cluster. Administrators may use this to restrict which devices may get requested by only installing classes with selectors for permitted devices. If users are free to request anything without restrictions, then administrators can create an empty DeviceClass for users to reference.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name can be used to reference this request in a pod.spec.containers[].resources.claims entry and in a constraint of the claim. Must be a DNS label.</TD></TR>
<TR><TD><CODE>selectors</CODE><BR /><I><a href="#deviceselector-v1beta1-resource-k8s-io">DeviceSelector</a> array</I></TD><TD>Selectors define criteria which must be satisfied by a specific device in order for that device to be considered for this request. All selectors must be satisfied for a device to be considered.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="devicerequestallocationresult-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceRequestAllocationResult</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceRequestAllocationResult</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceRequestAllocationResult contains the allocation result for one request.</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="#devicerequestallocationresult-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceallocationresult-v1beta1-resource-k8s-io">DeviceAllocationResult [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>adminAccess</CODE><BR /><I>boolean</I></TD><TD>AdminAccess indicates that this device was allocated for administrative access. See the corresponding request field for a definition of mode. This is an alpha field and requires enabling the DRAAdminAccess feature gate. Admin access is disabled if this field is unset or set to false, otherwise it is enabled.</TD></TR>
<TR><TD><CODE>device</CODE><BR /><I>string</I></TD><TD>Device references one device instance via its name in the driver&#39;s resource pool. It must be a DNS label.</TD></TR>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver specifies the name of the DRA driver whose kubelet plugin should be invoked to process the allocation once the claim is needed on a node. Must be a DNS subdomain and should end with a DNS domain owned by the vendor of the driver.</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>This name together with the driver name and the device name field identify which device was allocated (`&lt;driver name&gt;/&lt;pool name&gt;/&lt;device name&gt;`). Must not be longer than 253 characters and may contain one or more DNS sub-domains separated by slashes.</TD></TR>
<TR><TD><CODE>request</CODE><BR /><I>string</I></TD><TD>Request is the name of the request in the claim which caused this device to be allocated. Multiple devices may have been allocated per request.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="deviceselector-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">DeviceSelector</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeviceSelector</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeviceSelector must have exactly one field 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="#deviceselector-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceclassspec-v1beta1-resource-k8s-io">DeviceClassSpec [resource/v1beta1]</a></LI>
<LI><a href="#devicerequest-v1beta1-resource-k8s-io">DeviceRequest [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>cel</CODE><BR /><I><a href="#celdeviceselector-v1beta1-resource-k8s-io">CELDeviceSelector</a></I></TD><TD>CEL contains a CEL expression for selecting a device.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="downwardapiprojection-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">DownwardAPIProjection</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="downwardapivolumefile-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">DownwardAPIVolumeFile</span> <span class="v">v1</span> <span class="g">core</span></span></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, namespace and uid are supported.</TD></TR>
<TR><TD><CODE>mode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits used to set permissions on this file, must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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>
</DIV>
<DIV class="definition-container" id="downwardapivolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">DownwardAPIVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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 Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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>
</DIV>
<DIV class="definition-container" id="emptydirvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EmptyDirVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>medium represents 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>sizeLimit is the 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: https://kubernetes.io/docs/concepts/storage/volumes#emptydir</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="endpoint-v1-discovery-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">Endpoint</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Endpoint</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Endpoint represents a single logical &#34;backend&#34; implementing a service.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice [discovery/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>addresses</CODE><BR /><I>string array</I></TD><TD>addresses of this endpoint. The contents of this field are interpreted according to the corresponding EndpointSlice addressType field. Consumers must handle different types of addresses in the context of their own capabilities. This must contain at least one address but no more than 100. These are all assumed to be fungible and clients may choose to only use the first element. Refer to: https://issue.k8s.io/106267</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#endpointconditions-v1-discovery-k8s-io">EndpointConditions</a></I></TD><TD>conditions contains information about the current status of the endpoint.</TD></TR>
<TR><TD><CODE>deprecatedTopology</CODE><BR /><I>object</I></TD><TD>deprecatedTopology contains topology information part of the v1beta1 API. This field is deprecated, and will be removed when the v1beta1 API is removed (no sooner than kubernetes v1.24). While this field can hold values, it is not writable through the v1 API, and any attempts to write to it will be silently ignored. Topology information can be found in the zone and nodeName fields instead.</TD></TR>
<TR><TD><CODE>hints</CODE><BR /><I><a href="#endpointhints-v1-discovery-k8s-io">EndpointHints</a></I></TD><TD>hints contains information associated with how an endpoint should be consumed.</TD></TR>
<TR><TD><CODE>hostname</CODE><BR /><I>string</I></TD><TD>hostname of this endpoint. This field may be used by consumers of endpoints to distinguish endpoints from each other (e.g. in DNS names). Multiple endpoints which use the same hostname should be considered fungible (e.g. multiple A values in DNS). Must be lowercase and pass DNS Label (RFC 1123) validation.</TD></TR>
<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>nodeName represents the name of the 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>targetRef is a reference to a Kubernetes object that represents this endpoint.</TD></TR>
<TR><TD><CODE>zone</CODE><BR /><I>string</I></TD><TD>zone is the name of the Zone this endpoint exists in.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="endpointaddress-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EndpointAddress</span> <span class="v">v1</span> <span class="g">core</span></span></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 or ::1), link-local (169.254.0.0/16 or fe80::/10), or link-local multicast (224.0.0.0/24 or ff02::/16).</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>
</DIV>
<DIV class="definition-container" id="endpointconditions-v1-discovery-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">EndpointConditions</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointConditions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EndpointConditions represents the current condition of an endpoint.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#endpoint-v1-discovery-k8s-io">Endpoint [discovery/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ready</CODE><BR /><I>boolean</I></TD><TD>ready indicates that this endpoint is prepared to receive traffic, according to whatever system is managing the endpoint. A nil value indicates an unknown state. In most cases consumers should interpret this unknown state as ready. For compatibility reasons, ready should never be &#34;true&#34; for terminating endpoints, except when the normal readiness behavior is being explicitly overridden, for example when the associated Service has set the publishNotReadyAddresses flag.</TD></TR>
<TR><TD><CODE>serving</CODE><BR /><I>boolean</I></TD><TD>serving is identical to ready except that it is set regardless of the terminating state of endpoints. This condition should be set to true for a ready endpoint that is terminating. If nil, consumers should defer to the ready condition.</TD></TR>
<TR><TD><CODE>terminating</CODE><BR /><I>boolean</I></TD><TD>terminating indicates that this endpoint is terminating. A nil value indicates an unknown state. Consumers should interpret this unknown state to mean that the endpoint is not terminating.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="endpointhints-v1-discovery-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">EndpointHints</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointHints</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EndpointHints provides hints describing how an endpoint should be consumed.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#endpoint-v1-discovery-k8s-io">Endpoint [discovery/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>forZones</CODE><BR /><I><a href="#forzone-v1-discovery-k8s-io">ForZone</a> array</I></TD><TD>forZones indicates the zone(s) this endpoint should be consumed by to enable topology aware routing.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="endpointport-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EndpointPort</span> <span class="v">v1</span> <span class="g">core</span></span></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>appProtocol</CODE><BR /><I>string</I></TD><TD>The application protocol for this port. This is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either: * Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). * Kubernetes-defined prefixed names: * &#39;kubernetes.io/h2c&#39; - HTTP/2 prior knowledge over cleartext as described in https://www.rfc-editor.org/rfc/rfc9113.html#name-starting-http-2-with-prior- * &#39;kubernetes.io/ws&#39; - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455 * &#39;kubernetes.io/wss&#39; - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455 * Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of this port. This must match the &#39;name&#39; field in the corresponding ServicePort. 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, TCP, or SCTP. Default is TCP.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="endpointsubset-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EndpointSubset</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="envfromsource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EnvFromSource</span> <span class="v">v1</span> <span class="g">core</span></span></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="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</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>
</DIV>
<DIV class="definition-container" id="envvar-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EnvVar</span> <span class="v">v1</span> <span class="g">core</span></span></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="#ephemeralcontainer-v1-core">EphemeralContainer [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 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 previously 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. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. 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>
</DIV>
<DIV class="definition-container" id="envvarsource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EnvVarSource</span> <span class="v">v1</span> <span class="g">core</span></span></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[&#39;&lt;KEY&gt;&#39;]`, `metadata.annotations[&#39;&lt;KEY&gt;&#39;]`, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.</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>
</DIV>
<DIV class="definition-container" id="ephemeralcontainer-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EphemeralContainer</span> <span class="v">v1</span> <span class="g">core</span></span></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>EphemeralContainer</CODE></TD></TR>
</TBODY>
</TABLE>
<P>An EphemeralContainer is a temporary container that you may add to an existing Pod for user-initiated activities such as debugging. Ephemeral containers have no resource or scheduling guarantees, and they will not be restarted when they exit or when a Pod is removed or restarted. The kubelet may evict a Pod if an ephemeral container causes the Pod to exceed its resource allocation.
To add an ephemeral container, use the ephemeralcontainers subresource of an existing Pod. Ephemeral containers may not be removed or restarted.</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>args</CODE><BR /><I>string array</I></TD><TD>Arguments to the entrypoint. The 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. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. 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 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. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. &#34;$$(VAR_NAME)&#34; will produce the string literal &#34;$(VAR_NAME)&#34;. 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>Container image name. More info: https://kubernetes.io/docs/concepts/containers/images</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>Lifecycle is not allowed for ephemeral containers.</TD></TR>
<TR><TD><CODE>livenessProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Probes are not allowed for ephemeral containers.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the ephemeral container specified as a DNS_LABEL. This name must be unique among all containers, init containers and ephemeral containers.</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>Ports are not allowed for ephemeral containers.</TD></TR>
<TR><TD><CODE>readinessProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Probes are not allowed for ephemeral containers.</TD></TR>
<TR><TD><CODE>resizePolicy</CODE><BR /><I><a href="#containerresizepolicy-v1-core">ContainerResizePolicy</a> array</I></TD><TD>Resources resize policy for the container.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcerequirements-v1-core">ResourceRequirements</a></I></TD><TD>Resources are not allowed for ephemeral containers. Ephemeral containers use spare resources already allocated to the pod.</TD></TR>
<TR><TD><CODE>restartPolicy</CODE><BR /><I>string</I></TD><TD>Restart policy for the container to manage the restart behavior of each container within a pod. This may only be set for init containers. You cannot set this field on ephemeral containers.</TD></TR>
<TR><TD><CODE>securityContext</CODE><BR /><I><a href="#securitycontext-v1-core">SecurityContext</a></I></TD><TD>Optional: SecurityContext defines the security options the ephemeral container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext.</TD></TR>
<TR><TD><CODE>startupProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Probes are not allowed for ephemeral containers.</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>targetContainerName</CODE><BR /><I>string</I></TD><TD>If set, the name of the container from PodSpec that this ephemeral container targets. The ephemeral container will be run in the namespaces (IPC, PID, etc) of this container. If not set then the ephemeral container uses the namespaces configured in the Pod spec. The container runtime must implement support for this feature. If the runtime does not support namespace targeting then the result of setting this field is undefined.</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.</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. Subpath mounts are not allowed for ephemeral containers. 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>
</DIV>
<DIV class="definition-container" id="ephemeralvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EphemeralVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>EphemeralVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents an ephemeral volume that is handled by a normal storage driver.</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>volumeClaimTemplate</CODE><BR /><I><a href="#persistentvolumeclaimtemplate-v1-core">PersistentVolumeClaimTemplate</a></I></TD><TD>Will be used to create a stand-alone PVC to provision the volume. The pod in which this EphemeralVolumeSource is embedded will be the owner of the PVC, i.e. the PVC will be deleted together with the pod. The name of the PVC will be `&lt;pod name&gt;-&lt;volume name&gt;` where `&lt;volume name&gt;` is the name from the `PodSpec.Volumes` array entry. Pod validation will reject the pod if the concatenated name is not valid for a PVC (for example, too long). An existing PVC with that name that is not owned by the pod will *not* be used for the pod to avoid using an unrelated volume by mistake. Starting the pod is then blocked until the unrelated PVC is removed. If such a pre-created PVC is meant to be used by the pod, the PVC has to updated with an owner reference to the pod once the pod exists. Normally this should not be necessary, but it may be useful when manually reconstructing a broken cluster. This field is read-only and no changes will be made by Kubernetes to the PVC after it has been created. Required, must not be nil.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="eventseries-v1-events-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">EventSeries</span> <span class="v">v1</span> <span class="g">events.k8s.io</span></span></H2>
<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>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. How often to update the EventSeries is up to the event reporters. The default event reporter in &#34;k8s.io/client-go/tools/events/event_broadcaster.go&#34; shows how this struct is updated on heartbeats and can guide customized reporter implementations.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#event-v1-events-k8s-io">Event [events/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>count is the 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>lastObservedTime is the time when last Event from the series was seen before last heartbeat.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="eventsource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">EventSource</span> <span class="v">v1</span> <span class="g">core</span></span></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-v1-events-k8s-io">Event [events/v1]</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>
</DIV>
<DIV class="definition-container" id="eviction-v1-policy">
<H2 class="definition"><span class="gvk"><span class="k">Eviction</span> <span class="v">v1</span> <span class="g">policy</span></span></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>v1</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/sig-architecture/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/sig-architecture/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>
</DIV>
<DIV class="definition-container" id="execaction-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ExecAction</span> <span class="v">v1</span> <span class="g">core</span></span></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="#lifecyclehandler-v1-core">LifecycleHandler [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>
</DIV>
<DIV class="definition-container" id="exemptprioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ExemptPriorityLevelConfiguration</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ExemptPriorityLevelConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ExemptPriorityLevelConfiguration describes the configurable aspects of the handling of exempt requests. In the mandatory exempt configuration object the values in the fields here can be modified by authorized users, unlike the rest of the `spec`.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#prioritylevelconfigurationspec-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec [flowcontrol/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lendablePercent</CODE><BR /><I>integer</I></TD><TD>`lendablePercent` prescribes the fraction of the level&#39;s NominalCL that can be borrowed by other priority levels. This value of this field must be between 0 and 100, inclusive, and it defaults to 0. The number of seats that other levels can borrow from this level, known as this level&#39;s LendableConcurrencyLimit (LendableCL), is defined as follows. LendableCL(i) = round( NominalCL(i) * lendablePercent(i)/100.0 )</TD></TR>
<TR><TD><CODE>nominalConcurrencyShares</CODE><BR /><I>integer</I></TD><TD>`nominalConcurrencyShares` (NCS) contributes to the computation of the NominalConcurrencyLimit (NominalCL) of this level. This is the number of execution seats nominally reserved for this priority level. This DOES NOT limit the dispatching from this priority level but affects the other priority levels through the borrowing mechanism. The server&#39;s concurrency limit (ServerCL) is divided among all the priority levels in proportion to their NCS values: NominalCL(i) = ceil( ServerCL * NCS(i) / sum_ncs ) sum_ncs = sum[priority level k] NCS(k) Bigger numbers mean a larger nominal concurrency limit, at the expense of every other priority level. This field has a default value of zero.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="expressionwarning-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ExpressionWarning</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>ExpressionWarning</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ExpressionWarning is a warning information that targets a specific expression.</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="#expressionwarning-v1beta1-admissionregistration-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="#typechecking-v1-admissionregistration-k8s-io">TypeChecking [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fieldRef</CODE><BR /><I>string</I></TD><TD>The path to the field that refers the expression. For example, the reference to the expression of the first item of validations is &#34;spec.validations[0].expression&#34;</TD></TR>
<TR><TD><CODE>warning</CODE><BR /><I>string</I></TD><TD>The content of type checking information in a human-readable form. Each line of the warning contains the type that the expression is checked against, followed by the type check error from the compiler.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="externaldocumentation-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ExternalDocumentation</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</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>
</DIV>
<DIV class="definition-container" id="externalmetricsource-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">ExternalMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#metricspec-v2-autoscaling">MetricSpec [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="externalmetricstatus-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">ExternalMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="fcvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">FCVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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>lun is Optional: FC target lun number</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly is 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>targetWWNs is Optional: FC target worldwide names (WWNs)</TD></TR>
<TR><TD><CODE>wwids</CODE><BR /><I>string array</I></TD><TD>wwids 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>
</DIV>
<DIV class="definition-container" id="fieldselectorattributes-v1-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">FieldSelectorAttributes</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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>FieldSelectorAttributes</CODE></TD></TR>
</TBODY>
</TABLE>
<P>FieldSelectorAttributes indicates a field limited access. Webhook authors are encouraged to * ensure rawSelector and requirements are not both set * consider the requirements field if set * not try to parse or consider the rawSelector field if set. This is to avoid another CVE-2022-2880 (i.e. getting different systems to agree on how exactly to parse a query is not something we want), see https://www.oxeye.io/resources/golang-parameter-smuggling-attack for more details. For the *SubjectAccessReview endpoints of the kube-apiserver: * If rawSelector is empty and requirements are empty, the request is not limited. * If rawSelector is present and requirements are empty, the rawSelector will be parsed and limited if the parsing succeeds. * If rawSelector is empty and requirements are present, the requirements should be honored * If rawSelector is present and requirements are present, the request is invalid.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceattributes-v1-authorization-k8s-io">ResourceAttributes [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rawSelector</CODE><BR /><I>string</I></TD><TD>rawSelector is the serialization of a field selector that would be included in a query parameter. Webhook implementations are encouraged to ignore rawSelector. The kube-apiserver&#39;s *SubjectAccessReview will parse the rawSelector as long as the requirements are not present.</TD></TR>
<TR><TD><CODE>requirements</CODE><BR /><I><a href="#fieldselectorrequirement-v1-meta">FieldSelectorRequirement</a> array</I></TD><TD>requirements is the parsed interpretation of a field selector. All requirements must be met for a resource instance to match the selector. Webhook implementations should handle requirements, but how to handle them is up to the webhook. Since requirements can only limit the request, it is safe to authorize as unlimited request if the requirements are not understood.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="fieldselectorrequirement-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">FieldSelectorRequirement</span> <span class="v">v1</span> <span class="g">meta</span></span></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>FieldSelectorRequirement</CODE></TD></TR>
</TBODY>
</TABLE>
<P>FieldSelectorRequirement 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="#fieldselectorattributes-v1-authorization-k8s-io">FieldSelectorAttributes [authorization/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>key is the field selector key that the requirement 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, DoesNotExist. The list of operators may grow in the future.</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.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="fieldsv1-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">FieldsV1</span> <span class="v">v1</span> <span class="g">meta</span></span></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>FieldsV1</CODE></TD></TR>
</TBODY>
</TABLE>
<P>FieldsV1 stores a set of fields in a data structure like a Trie, in JSON format.
Each key is either a &#39;.&#39; representing the field itself, and will always map to an empty set, or a string representing a sub-field or item. The string will follow one of these four formats: &#39;f:&lt;name&gt;&#39;, where &lt;name&gt; is the name of a field in a struct, or key in a map &#39;v:&lt;value&gt;&#39;, where &lt;value&gt; is the exact json formatted value of a list item &#39;i:&lt;index&gt;&#39;, where &lt;index&gt; is position of a item in a list &#39;k:&lt;keys&gt;&#39;, where &lt;keys&gt; is a map of a list item&#39;s key fields to their unique values If a key maps to an empty Fields value, the field that key represents is part of the set.
The exact format is defined in sigs.k8s.io/structured-merge-diff</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#managedfieldsentry-v1-meta">ManagedFieldsEntry [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="flexpersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">FlexPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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>options is Optional: this field holds extra command options if any.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly is 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>secretRef is 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>
</DIV>
<DIV class="definition-container" id="flexvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">FlexVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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>options is Optional: this field holds extra command options if any.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly is 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>secretRef is 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>
</DIV>
<DIV class="definition-container" id="flockervolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">FlockerVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>datasetName is 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>datasetUUID is the UUID of the dataset. This is unique identifier of a Flocker dataset</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="flowdistinguishermethod-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">FlowDistinguisherMethod</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FlowDistinguisherMethod</CODE></TD></TR>
</TBODY>
</TABLE>
<P>FlowDistinguisherMethod specifies the method of a flow distinguisher.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#flowschemaspec-v1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is the type of flow distinguisher method The supported types are &#34;ByUser&#34; and &#34;ByNamespace&#34;. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="flowschemacondition-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">FlowSchemaCondition</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FlowSchemaCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>FlowSchemaCondition describes conditions for a FlowSchema.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#flowschemastatus-v1-flowcontrol-apiserver-k8s-io">FlowSchemaStatus [flowcontrol/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>`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 message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>`reason` is a 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. Required.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is the type of the condition. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="forzone-v1-discovery-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ForZone</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ForZone</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ForZone provides information about which zones should consume this endpoint.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#endpointhints-v1-discovery-k8s-io">EndpointHints [discovery/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 represents the name of the zone.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="gcepersistentdiskvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">GCEPersistentDiskVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is 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>partition is 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>pdName is 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>
</DIV>
<DIV class="definition-container" id="grpcaction-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">GRPCAction</span> <span class="v">v1</span> <span class="g">core</span></span></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>GRPCAction</CODE></TD></TR>
</TBODY>
</TABLE>
<P>GRPCAction specifies an action involving a GRPC service.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<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>port</CODE><BR /><I>integer</I></TD><TD>Port number of the gRPC service. Number must be in the range 1 to 65535.</TD></TR>
<TR><TD><CODE>service</CODE><BR /><I>string</I></TD><TD>Service is the name of the service to place in the gRPC HealthCheckRequest (see https://github.com/grpc/grpc/blob/master/doc/health-checking.md). If this is not specified, the default behavior is defined by gRPC.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="gitrepovolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">GitRepoVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>directory is the 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 is the URL</TD></TR>
<TR><TD><CODE>revision</CODE><BR /><I>string</I></TD><TD>revision is the commit hash for the specified revision.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="glusterfspersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">GlusterfsPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>GlusterfsPersistentVolumeSource</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>
</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>endpoints is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
<TR><TD><CODE>endpointsNamespace</CODE><BR /><I>string</I></TD><TD>endpointsNamespace is the namespace that contains Glusterfs endpoint. If this field is empty, the EndpointNamespace defaults to the same namespace as the bound PVC. More info: https://examples.k8s.io/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://examples.k8s.io/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://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="glusterfsvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">GlusterfsVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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="#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>endpoints is the endpoint name that details Glusterfs topology. More info: https://examples.k8s.io/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://examples.k8s.io/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://examples.k8s.io/volumes/glusterfs/README.md#create-a-pod</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="groupsubject-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">GroupSubject</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GroupSubject</CODE></TD></TR>
</TBODY>
</TABLE>
<P>GroupSubject holds detailed information for group-kind subject.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#subject-v1-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/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 user group that matches, or &#34;*&#34; to match all user groups. See https://github.com/kubernetes/apiserver/blob/master/pkg/authentication/user/user.go for some well-known group names. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="groupversionfordiscovery-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">GroupVersionForDiscovery</span> <span class="v">v1</span> <span class="g">meta</span></span></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>
</DIV>
<DIV class="definition-container" id="groupversionresource-v1alpha1-storagemigration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">GroupVersionResource</span> <span class="v">v1alpha1</span> <span class="g">storagemigration.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storagemigration.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>GroupVersionResource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>The names of the group, the version, and the resource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageversionmigrationspec-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationSpec [storagemigration/v1alpha1]</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>The name of the group.</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>The name of the resource.</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>The name of the version.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="hpascalingpolicy-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">HPAScalingPolicy</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</CODE></TD><TD><CODE>HPAScalingPolicy</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HPAScalingPolicy is a single policy which must hold true for a specified past interval.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#hpascalingrules-v2-autoscaling">HPAScalingRules [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>periodSeconds</CODE><BR /><I>integer</I></TD><TD>periodSeconds specifies the window of time for which the policy should hold true. PeriodSeconds must be greater than zero and less than or equal to 1800 (30 min).</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is used to specify the scaling policy.</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>integer</I></TD><TD>value contains the amount of change which is permitted by the policy. It must be greater than zero</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="hpascalingrules-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">HPAScalingRules</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</CODE></TD><TD><CODE>HPAScalingRules</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HPAScalingRules configures the scaling behavior for one direction. These Rules are applied after calculating DesiredReplicas from metrics for the HPA. They can limit the scaling velocity by specifying scaling policies. They can prevent flapping by specifying the stabilization window, so that the number of replicas is not set instantly, instead, the safest value from the stabilization window is chosen.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscalerbehavior-v2-autoscaling">HorizontalPodAutoscalerBehavior [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policies</CODE><BR /><I><a href="#hpascalingpolicy-v2-autoscaling">HPAScalingPolicy</a> array</I></TD><TD>policies is a list of potential scaling polices which can be used during scaling. At least one policy must be specified, otherwise the HPAScalingRules will be discarded as invalid</TD></TR>
<TR><TD><CODE>selectPolicy</CODE><BR /><I>string</I></TD><TD>selectPolicy is used to specify which policy should be used. If not set, the default value Max is used.</TD></TR>
<TR><TD><CODE>stabilizationWindowSeconds</CODE><BR /><I>integer</I></TD><TD>stabilizationWindowSeconds is the number of seconds for which past recommendations should be considered while scaling up or scaling down. StabilizationWindowSeconds must be greater than or equal to zero and less than or equal to 3600 (one hour). If not set, use the default values: - For scale up: 0 (i.e. no stabilization is done). - For scale down: 300 (i.e. the stabilization window is 300 seconds long).</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="httpgetaction-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">HTTPGetAction</span> <span class="v">v1</span> <span class="g">core</span></span></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="#lifecyclehandler-v1-core">LifecycleHandler [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>
</DIV>
<DIV class="definition-container" id="httpheader-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">HTTPHeader</span> <span class="v">v1</span> <span class="g">core</span></span></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. This will be canonicalized upon output, so case-variant names will be understood as the same header.</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>The header field value</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="httpingresspath-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">HTTPIngressPath</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>HTTPIngressPath</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HTTPIngressPath associates a path 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-v1-networking-k8s-io">HTTPIngressRuleValue [networking/v1]</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-v1-networking-k8s-io">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 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; and must be present when using PathType with value &#34;Exact&#34; or &#34;Prefix&#34;.</TD></TR>
<TR><TD><CODE>pathType</CODE><BR /><I>string</I></TD><TD>pathType determines the interpretation of the path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by &#39;/&#39;. Matching is done on a path element by element basis. A path element refers is the list of labels in the path split by the &#39;/&#39; separator. A request is a match for path p if every p is an element-wise prefix of p of the request path. Note that if the last element of the path is a substring of the last element in request path, it is not a match (e.g. /foo/bar matches /foo/bar/baz, but does not match /foo/barbaz). * ImplementationSpecific: Interpretation of the Path matching is up to the IngressClass. Implementations can treat this as a separate PathType or treat it identically to Prefix or Exact path types. Implementations are required to support all path types.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="httpingressrulevalue-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">HTTPIngressRuleValue</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>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-v1-networking-k8s-io">IngressRule [networking/v1]</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-v1-networking-k8s-io">HTTPIngressPath</a> array</I></TD><TD>paths is a collection of paths that map requests to backends.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="horizontalpodautoscalerbehavior-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">HorizontalPodAutoscalerBehavior</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</CODE></TD><TD><CODE>HorizontalPodAutoscalerBehavior</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HorizontalPodAutoscalerBehavior configures the scaling behavior of the target in both Up and Down directions (scaleUp and scaleDown fields respectively).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscalerspec-v2-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>scaleDown</CODE><BR /><I><a href="#hpascalingrules-v2-autoscaling">HPAScalingRules</a></I></TD><TD>scaleDown is scaling policy for scaling Down. If not set, the default value is to allow to scale down to minReplicas pods, with a 300 second stabilization window (i.e., the highest recommendation for the last 300sec is used).</TD></TR>
<TR><TD><CODE>scaleUp</CODE><BR /><I><a href="#hpascalingrules-v2-autoscaling">HPAScalingRules</a></I></TD><TD>scaleUp is scaling policy for scaling Up. If not set, the default value is the higher of: * increase no more than 4 pods per 60 seconds * double the number of pods per 60 seconds No stabilization is used.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="horizontalpodautoscalercondition-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">HorizontalPodAutoscalerCondition</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2]</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>
</DIV>
<DIV class="definition-container" id="hostalias-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">HostAlias</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="hostip-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">HostIP</span> <span class="v">v1</span> <span class="g">core</span></span></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>HostIP</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HostIP represents a single IP address allocated to the host.</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>ip</CODE><BR /><I>string</I></TD><TD>IP is the IP address assigned to the host</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="hostpathvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">HostPathVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="ipblock-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">IPBlock</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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.0/24&#34;,&#34;2001:db8::/64&#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-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 IPBlock Valid examples are &#34;192.168.1.0/24&#34; or &#34;2001:db8::/64&#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 IPBlock Valid examples are &#34;192.168.1.0/24&#34; or &#34;2001:db8::/64&#34; Except values will be rejected if they are outside the cidr range</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="iscsipersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ISCSIPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>chapAuthDiscovery defines whether support iSCSI Discovery CHAP authentication</TD></TR>
<TR><TD><CODE>chapAuthSession</CODE><BR /><I>boolean</I></TD><TD>chapAuthSession defines whether support iSCSI Session CHAP authentication</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>fsType is the 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>initiatorName is the 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>iqn is Target iSCSI Qualified Name.</TD></TR>
<TR><TD><CODE>iscsiInterface</CODE><BR /><I>string</I></TD><TD>iscsiInterface is the 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>lun is iSCSI Target Lun number.</TD></TR>
<TR><TD><CODE>portals</CODE><BR /><I>string array</I></TD><TD>portals is the 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>secretRef is the CHAP Secret for iSCSI target and initiator authentication</TD></TR>
<TR><TD><CODE>targetPortal</CODE><BR /><I>string</I></TD><TD>targetPortal is 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>
</DIV>
<DIV class="definition-container" id="iscsivolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ISCSIVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>chapAuthDiscovery defines whether support iSCSI Discovery CHAP authentication</TD></TR>
<TR><TD><CODE>chapAuthSession</CODE><BR /><I>boolean</I></TD><TD>chapAuthSession defines whether support iSCSI Session CHAP authentication</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>fsType is the 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>initiatorName is the 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>iqn is the target iSCSI Qualified Name.</TD></TR>
<TR><TD><CODE>iscsiInterface</CODE><BR /><I>string</I></TD><TD>iscsiInterface is the 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>lun represents iSCSI Target Lun number.</TD></TR>
<TR><TD><CODE>portals</CODE><BR /><I>string array</I></TD><TD>portals is the 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>secretRef is the CHAP Secret for iSCSI target and initiator authentication</TD></TR>
<TR><TD><CODE>targetPortal</CODE><BR /><I>string</I></TD><TD>targetPortal is 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>
</DIV>
<DIV class="definition-container" id="imagevolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ImageVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>ImageVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ImageVolumeSource represents a image 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>pullPolicy</CODE><BR /><I>string</I></TD><TD>Policy for pulling OCI objects. Possible values are: Always: the kubelet always attempts to pull the reference. Container creation will fail If the pull fails. Never: the kubelet never pulls the reference and only uses a local image or artifact. Container creation will fail if the reference isn&#39;t present. IfNotPresent: the kubelet pulls if the reference isn&#39;t already present on disk. Container creation will fail if the reference isn&#39;t present and the pull fails. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise.</TD></TR>
<TR><TD><CODE>reference</CODE><BR /><I>string</I></TD><TD>Required: Image or artifact reference to be used. Behaves in the same way as pod.spec.containers[*].image. Pull secrets will be assembled in the same way as for the container image by looking up node credentials, SA image pull secrets, and pod spec image pull secrets. 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>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="ingressbackend-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">IngressBackend</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>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-v1-networking-k8s-io">HTTPIngressPath [networking/v1]</a></LI>
<LI><a href="#ingressspec-v1-networking-k8s-io">IngressSpec [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource</CODE><BR /><I><a href="#typedlocalobjectreference-v1-core">TypedLocalObjectReference</a></I></TD><TD>resource is an ObjectRef to another Kubernetes resource in the namespace of the Ingress object. If resource is specified, a service.Name and service.Port must not be specified. This is a mutually exclusive setting with &#34;Service&#34;.</TD></TR>
<TR><TD><CODE>service</CODE><BR /><I><a href="#ingressservicebackend-v1-networking-k8s-io">IngressServiceBackend</a></I></TD><TD>service references a service as a backend. This is a mutually exclusive setting with &#34;Resource&#34;.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="ingressclassparametersreference-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">IngressClassParametersReference</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>IngressClassParametersReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IngressClassParametersReference identifies an API object. This can be used to specify a cluster or namespace-scoped resource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressclassspec-v1-networking-k8s-io">IngressClassSpec [networking/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. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.</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>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>namespace is the namespace of the resource being referenced. This field is required when scope is set to &#34;Namespace&#34; and must be unset when scope is set to &#34;Cluster&#34;.</TD></TR>
<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>scope represents if this refers to a cluster or namespace scoped resource. This may be set to &#34;Cluster&#34; (default) or &#34;Namespace&#34;.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="ingressloadbalanceringress-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">IngressLoadBalancerIngress</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>IngressLoadBalancerIngress</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IngressLoadBalancerIngress represents the status of a load-balancer ingress point.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressloadbalancerstatus-v1-networking-k8s-io">IngressLoadBalancerStatus [networking/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.</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.</TD></TR>
<TR><TD><CODE>ports</CODE><BR /><I><a href="#ingressportstatus-v1-networking-k8s-io">IngressPortStatus</a> array</I></TD><TD>ports provides information about the ports exposed by this LoadBalancer.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="ingressloadbalancerstatus-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">IngressLoadBalancerStatus</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>IngressLoadBalancerStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IngressLoadBalancerStatus 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-v1-networking-k8s-io">IngressStatus [networking/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="#ingressloadbalanceringress-v1-networking-k8s-io">IngressLoadBalancerIngress</a> array</I></TD><TD>ingress is a list containing ingress points for the load-balancer.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="ingressportstatus-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">IngressPortStatus</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>IngressPortStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IngressPortStatus represents the error condition of a service port</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressloadbalanceringress-v1-networking-k8s-io">IngressLoadBalancerIngress [networking/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>error is to record the problem with the service port The format of the error shall comply with the following rules: - built-in error values shall be specified in this file and those shall use CamelCase names - cloud provider specific error values must have names that comply with the format foo.example.com/CamelCase.</TD></TR>
<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>port is the port number of the ingress port.</TD></TR>
<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>protocol is the protocol of the ingress port. The supported values are: &#34;TCP&#34;, &#34;UDP&#34;, &#34;SCTP&#34;</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="ingressrule-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">IngressRule</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>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-v1-networking-k8s-io">IngressSpec [networking/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 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 RFC 3986: 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. host can be &#34;precise&#34; which is a domain name without the terminating dot of a network host (e.g. &#34;foo.bar.com&#34;) or &#34;wildcard&#34;, which is a domain name prefixed with a single wildcard label (e.g. &#34;*.foo.com&#34;). The wildcard character &#39;\*&#39; must appear by itself as the first DNS label and matches only a single label. You cannot have a wildcard label by itself (e.g. Host == &#34;*&#34;). Requests will be matched against the Host field in the following way: 1. If host is precise, the request matches this rule if the http host header is equal to Host. 2. If host is a wildcard, then the request matches this rule if the http host header is to equal to the suffix (removing the first label) of the wildcard rule.</TD></TR>
<TR><TD><CODE>http</CODE><BR /><I><a href="#httpingressrulevalue-v1-networking-k8s-io">HTTPIngressRuleValue</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="ingressservicebackend-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">IngressServiceBackend</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>IngressServiceBackend</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IngressServiceBackend references a Kubernetes Service as a Backend.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressbackend-v1-networking-k8s-io">IngressBackend [networking/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 referenced service. The service must exist in the same namespace as the Ingress object.</TD></TR>
<TR><TD><CODE>port</CODE><BR /><I><a href="#servicebackendport-v1-networking-k8s-io">ServiceBackendPort</a></I></TD><TD>port of the referenced service. A port name or port number is required for a IngressServiceBackend.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="ingresstls-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">IngressTLS</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>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-v1-networking-k8s-io">IngressSpec [networking/v1]</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 is 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 TLS traffic on port 443. Field is left optional to allow TLS 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 &#34;Host&#34; header is used for routing.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="json-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">JSON</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="jsonpatch-v1alpha1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">JSONPatch</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>JSONPatch</CODE></TD></TR>
</TBODY>
</TABLE>
<P>JSONPatch defines a JSON Patch.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#mutation-v1alpha1-admissionregistration-k8s-io">Mutation [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>expression will be evaluated by CEL to create a [JSON patch](https://jsonpatch.com/). ref: https://github.com/google/cel-spec expression must return an array of JSONPatch values. For example, this CEL expression returns a JSON patch to conditionally modify a value: [ JSONPatch{op: &#34;test&#34;, path: &#34;/spec/example&#34;, value: &#34;Red&#34;}, JSONPatch{op: &#34;replace&#34;, path: &#34;/spec/example&#34;, value: &#34;Green&#34;} ] To define an object for the patch value, use Object types. For example: [ JSONPatch{ op: &#34;add&#34;, path: &#34;/spec/selector&#34;, value: Object.spec.selector{matchLabels: {&#34;environment&#34;: &#34;test&#34;}} } ] To use strings containing &#39;/&#39; and &#39;~&#39; as JSONPatch path keys, use &#34;jsonpatch.escapeKey&#34;. For example: [ JSONPatch{ op: &#34;add&#34;, path: &#34;/metadata/labels/&#34; + jsonpatch.escapeKey(&#34;example.com/environment&#34;), value: &#34;test&#34; }, ] CEL expressions have access to the types needed to create JSON patches and objects: - &#39;JSONPatch&#39; - CEL type of JSON Patch operations. JSONPatch has the fields &#39;op&#39;, &#39;from&#39;, &#39;path&#39; and &#39;value&#39;. See [JSON patch](https://jsonpatch.com/) for more details. The &#39;value&#39; field may be set to any of: string, integer, array, map or object. If set, the &#39;path&#39; and &#39;from&#39; fields must be set to a [JSON pointer](https://datatracker.ietf.org/doc/html/rfc6901/) string, where the &#39;jsonpatch.escapeKey()&#39; CEL function may be used to escape path keys containing &#39;/&#39; and &#39;~&#39;. - &#39;Object&#39; - CEL type of the resource object. - &#39;Object.&lt;fieldName&gt;&#39; - CEL type of object field (such as &#39;Object.spec&#39;) - &#39;Object.&lt;fieldName1&gt;.&lt;fieldName2&gt;...&lt;fieldNameN&gt;` - CEL type of nested field (such as &#39;Object.spec.containers&#39;) CEL expressions have access to the contents of the API request, organized into CEL variables as well as some other useful variables: - &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. - &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. - &#39;request&#39; - Attributes of the API request([ref](/pkg/apis/admission/types.go#AdmissionRequest)). - &#39;params&#39; - Parameter resource referred to by the policy binding being evaluated. Only populated if the policy has a ParamKind. - &#39;namespaceObject&#39; - The namespace object that the incoming object belongs to. The value is null for cluster-scoped resources. - &#39;variables&#39; - Map of composited variables, from its name to its lazily evaluated value. For example, a variable named &#39;foo&#39; can be accessed as &#39;variables.foo&#39;. - &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request. See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz - &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the request resource. CEL expressions have access to [Kubernetes CEL function libraries](https://kubernetes.io/docs/reference/using-api/cel/#cel-options-language-features-and-libraries) as well as: - &#39;jsonpatch.escapeKey&#39; - Performs JSONPatch key escaping. &#39;~&#39; and &#39;/&#39; are escaped as &#39;~0&#39; and `~1&#39; respectively). Only property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="jsonschemaprops-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">JSONSchemaProps</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">CustomResourceValidation [apiextensions/v1]</a></LI>
<LI><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</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-v1-apiextensions-k8s-io">JSONSchemaPropsOrBool</a></I></TD><TD></TD></TR>
<TR><TD><CODE>additionalProperties</CODE><BR /><I><a href="#jsonschemapropsorbool-v1-apiextensions-k8s-io">JSONSchemaPropsOrBool</a></I></TD><TD></TD></TR>
<TR><TD><CODE>allOf</CODE><BR /><I><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>anyOf</CODE><BR /><I><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>default</CODE><BR /><I><a href="#json-v1-apiextensions-k8s-io">JSON</a></I></TD><TD>default is a default value for undefined object fields. Defaulting is a beta feature under the CustomResourceDefaulting feature gate. Defaulting requires spec.preserveUnknownFields to be false.</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-v1-apiextensions-k8s-io">JSON</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>example</CODE><BR /><I><a href="#json-v1-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-v1-apiextensions-k8s-io">ExternalDocumentation</a></I></TD><TD></TD></TR>
<TR><TD><CODE>format</CODE><BR /><I>string</I></TD><TD>format is an OpenAPI v3 format string. Unknown formats are ignored. The following formats are validated: - bsonobjectid: a bson object ID, i.e. a 24 characters hex string - uri: an URI as parsed by Golang net/url.ParseRequestURI - email: an email address as parsed by Golang net/mail.ParseAddress - hostname: a valid representation for an Internet host name, as defined by RFC 1034, section 3.1 [RFC1034]. - ipv4: an IPv4 IP as parsed by Golang net.ParseIP - ipv6: an IPv6 IP as parsed by Golang net.ParseIP - cidr: a CIDR as parsed by Golang net.ParseCIDR - mac: a MAC address as parsed by Golang net.ParseMAC - uuid: an UUID that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?[0-9a-f]{4}-?[0-9a-f]{4}-?[0-9a-f]{12}$ - uuid3: an UUID3 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?3[0-9a-f]{3}-?[0-9a-f]{4}-?[0-9a-f]{12}$ - uuid4: an UUID4 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?4[0-9a-f]{3}-?[89ab][0-9a-f]{3}-?[0-9a-f]{12}$ - uuid5: an UUID5 that allows uppercase defined by the regex (?i)^[0-9a-f]{8}-?[0-9a-f]{4}-?5[0-9a-f]{3}-?[89ab][0-9a-f]{3}-?[0-9a-f]{12}$ - isbn: an ISBN10 or ISBN13 number string like &#34;0321751043&#34; or &#34;978-0321751041&#34; - isbn10: an ISBN10 number string like &#34;0321751043&#34; - isbn13: an ISBN13 number string like &#34;978-0321751041&#34; - creditcard: a credit card number defined by the regex ^(?:4[0-9]{12}(?:[0-9]{3})?|5[1-5][0-9]{14}|6(?:011|5[0-9][0-9])[0-9]{12}|3[47][0-9]{13}|3(?:0[0-5]|[68][0-9])[0-9]{11}|(?:2131|1800|35\\d{3})\\d{11})$ with any non digit characters mixed in - ssn: a U.S. social security number following the regex ^\\d{3}[- ]?\\d{2}[- ]?\\d{4}$ - hexcolor: an hexadecimal color code like &#34;#FFFFFF: following the regex ^#?([0-9a-fA-F]{3}|[0-9a-fA-F]{6})$ - rgbcolor: an RGB color code like rgb like &#34;rgb(255,255,2559&#34; - byte: base64 encoded binary data - password: any kind of string - date: a date string like &#34;2006-01-02&#34; as defined by full-date in RFC3339 - duration: a duration string like &#34;22 ns&#34; as parsed by Golang time.ParseDuration or compatible with Scala duration format - datetime: a date time string like &#34;2014-12-15T19:30:20.000Z&#34; as defined by date-time in RFC3339.</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-v1-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-v1-apiextensions-k8s-io">JSONSchemaProps</a></I></TD><TD></TD></TR>
<TR><TD><CODE>nullable</CODE><BR /><I>boolean</I></TD><TD></TD></TR>
<TR><TD><CODE>oneOf</CODE><BR /><I><a href="#jsonschemaprops-v1-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>
<TR><TD><CODE>x-kubernetes-embedded-resource</CODE><BR /><I>boolean</I></TD><TD>x-kubernetes-embedded-resource defines that the value is an embedded Kubernetes runtime.Object, with TypeMeta and ObjectMeta. The type must be object. It is allowed to further restrict the embedded object. kind, apiVersion and metadata are validated automatically. x-kubernetes-preserve-unknown-fields is allowed to be true, but does not have to be if the object is fully specified (up to kind, apiVersion, metadata).</TD></TR>
<TR><TD><CODE>x-kubernetes-int-or-string</CODE><BR /><I>boolean</I></TD><TD>x-kubernetes-int-or-string specifies that this value is either an integer or a string. If this is true, an empty type is allowed and type as child of anyOf is permitted if following one of the following patterns: 1) anyOf: - type: integer - type: string 2) allOf: - anyOf: - type: integer - type: string - ... zero or more</TD></TR>
<TR><TD><CODE>x-kubernetes-list-map-keys</CODE><BR /><I>string array</I></TD><TD>x-kubernetes-list-map-keys annotates an array with the x-kubernetes-list-type `map` by specifying the keys used as the index of the map. This tag MUST only be used on lists that have the &#34;x-kubernetes-list-type&#34; extension set to &#34;map&#34;. Also, the values specified for this attribute must be a scalar typed field of the child structure (no nesting is supported). The properties specified must either be required or have a default value, to ensure those properties are present for all list items.</TD></TR>
<TR><TD><CODE>x-kubernetes-list-type</CODE><BR /><I>string</I></TD><TD>x-kubernetes-list-type annotates an array to further describe its topology. This extension must only be used on lists and may have 3 possible values: 1) `atomic`: the list is treated as a single entity, like a scalar. Atomic lists will be entirely replaced when updated. This extension may be used on any type of list (struct, scalar, ...). 2) `set`: Sets are lists that must not have multiple items with the same value. Each value must be a scalar, an object with x-kubernetes-map-type `atomic` or an array with x-kubernetes-list-type `atomic`. 3) `map`: These lists are like maps in that their elements have a non-index key used to identify them. Order is preserved upon merge. The map tag must only be used on a list with elements of type object. Defaults to atomic for arrays.</TD></TR>
<TR><TD><CODE>x-kubernetes-map-type</CODE><BR /><I>string</I></TD><TD>x-kubernetes-map-type annotates an object to further describe its topology. This extension must only be used when type is object and may have 2 possible values: 1) `granular`: These maps are actual maps (key-value pairs) and each fields are independent from each other (they can each be manipulated by separate actors). This is the default behaviour for all maps. 2) `atomic`: the list is treated as a single entity, like a scalar. Atomic maps will be entirely replaced when updated.</TD></TR>
<TR><TD><CODE>x-kubernetes-preserve-unknown-fields</CODE><BR /><I>boolean</I></TD><TD>x-kubernetes-preserve-unknown-fields stops the API server decoding step from pruning fields which are not specified in the validation schema. This affects fields recursively, but switches back to normal pruning behaviour if nested properties or additionalProperties are specified in the schema. This can either be true or undefined. False is forbidden.</TD></TR>
<TR><TD><CODE>x-kubernetes-validations</CODE><BR /><I><a href="#validationrule-v1-apiextensions-k8s-io">ValidationRule</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>rule</I></TD><TD>x-kubernetes-validations describes a list of validation rules written in the CEL expression language.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="jsonschemapropsorarray-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">JSONSchemaPropsOrArray</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="jsonschemapropsorbool-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">JSONSchemaPropsOrBool</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</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-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="jobcondition-v1-batch">
<H2 class="definition"><span class="gvk"><span class="k">JobCondition</span> <span class="v">v1</span> <span class="g">batch</span></span></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>
</DIV>
<DIV class="definition-container" id="jobtemplatespec-v1-batch">
<H2 class="definition"><span class="gvk"><span class="k">JobTemplateSpec</span> <span class="v">v1</span> <span class="g">batch</span></span></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>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-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjobspec-v1-batch">CronJobSpec [batch/v1]</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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="keytopath-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">KeyToPath</span> <span class="v">v1</span> <span class="g">core</span></span></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>key is the key to project.</TD></TR>
<TR><TD><CODE>mode</CODE><BR /><I>integer</I></TD><TD>mode is Optional: mode bits used to set permissions on this file. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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>path is 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>
</DIV>
<DIV class="definition-container" id="labelselector-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">LabelSelector</span> <span class="v">v1</span> <span class="g">meta</span></span></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="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity [storage/v1]</a></LI>
<LI><a href="#clustertrustbundleprojection-v1-core">ClusterTrustBundleProjection [core/v1]</a></LI>
<LI><a href="#daemonsetspec-v1-apps">DaemonSetSpec [apps/v1]</a></LI>
<LI><a href="#deploymentspec-v1-apps">DeploymentSpec [apps/v1]</a></LI>
<LI><a href="#jobspec-v1-batch">JobSpec [batch/v1]</a></LI>
<LI><a href="#matchresources-v1-admissionregistration-k8s-io">MatchResources [admissionregistration/v1]</a></LI>
<LI><a href="#matchresources-v1beta1-admissionregistration-k8s-io">MatchResources [admissionregistration/v1beta1]</a></LI>
<LI><a href="#matchresources-v1alpha1-admissionregistration-k8s-io">MatchResources [admissionregistration/v1alpha1]</a></LI>
<LI><a href="#metricidentifier-v2-autoscaling">MetricIdentifier [autoscaling/v2]</a></LI>
<LI><a href="#mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook [admissionregistration/v1]</a></LI>
<LI><a href="#networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer [networking/v1]</a></LI>
<LI><a href="#networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec [networking/v1]</a></LI>
<LI><a href="#paramref-v1-admissionregistration-k8s-io">ParamRef [admissionregistration/v1]</a></LI>
<LI><a href="#paramref-v1beta1-admissionregistration-k8s-io">ParamRef [admissionregistration/v1beta1]</a></LI>
<LI><a href="#paramref-v1alpha1-admissionregistration-k8s-io">ParamRef [admissionregistration/v1alpha1]</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-v1-policy">PodDisruptionBudgetSpec [policy/v1]</a></LI>
<LI><a href="#replicasetspec-v1-apps">ReplicaSetSpec [apps/v1]</a></LI>
<LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
<LI><a href="#topologyspreadconstraint-v1-core">TopologySpreadConstraint [core/v1]</a></LI>
<LI><a href="#validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook [admissionregistration/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="#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>
</DIV>
<DIV class="definition-container" id="labelselectorattributes-v1-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">LabelSelectorAttributes</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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>LabelSelectorAttributes</CODE></TD></TR>
</TBODY>
</TABLE>
<P>LabelSelectorAttributes indicates a label limited access. Webhook authors are encouraged to * ensure rawSelector and requirements are not both set * consider the requirements field if set * not try to parse or consider the rawSelector field if set. This is to avoid another CVE-2022-2880 (i.e. getting different systems to agree on how exactly to parse a query is not something we want), see https://www.oxeye.io/resources/golang-parameter-smuggling-attack for more details. For the *SubjectAccessReview endpoints of the kube-apiserver: * If rawSelector is empty and requirements are empty, the request is not limited. * If rawSelector is present and requirements are empty, the rawSelector will be parsed and limited if the parsing succeeds. * If rawSelector is empty and requirements are present, the requirements should be honored * If rawSelector is present and requirements are present, the request is invalid.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceattributes-v1-authorization-k8s-io">ResourceAttributes [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rawSelector</CODE><BR /><I>string</I></TD><TD>rawSelector is the serialization of a field selector that would be included in a query parameter. Webhook implementations are encouraged to ignore rawSelector. The kube-apiserver&#39;s *SubjectAccessReview will parse the rawSelector as long as the requirements are not present.</TD></TR>
<TR><TD><CODE>requirements</CODE><BR /><I><a href="#labelselectorrequirement-v1-meta">LabelSelectorRequirement</a> array</I></TD><TD>requirements is the parsed interpretation of a label selector. All requirements must be met for a resource instance to match the selector. Webhook implementations should handle requirements, but how to handle them is up to the webhook. Since requirements can only limit the request, it is safe to authorize as unlimited request if the requirements are not understood.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="labelselectorrequirement-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">LabelSelectorRequirement</span> <span class="v">v1</span> <span class="g">meta</span></span></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>
<LI><a href="#labelselectorattributes-v1-authorization-k8s-io">LabelSelectorAttributes [authorization/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>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>
</DIV>
<DIV class="definition-container" id="lifecycle-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">Lifecycle</span> <span class="v">v1</span> <span class="g">core</span></span></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>
<LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [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="#lifecyclehandler-v1-core">LifecycleHandler</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="#lifecyclehandler-v1-core">LifecycleHandler</a></I></TD><TD>PreStop is called immediately before a container is terminated due to an API request or management event such as liveness/startup probe failure, preemption, resource contention, etc. The handler is not called if the container crashes or exits. The Pod&#39;s termination grace period countdown begins before the PreStop hook is executed. Regardless of the outcome of the handler, the container will eventually terminate within the Pod&#39;s termination grace period (unless delayed by finalizers). Other management of the container blocks until the hook completes or until the termination grace period is reached. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="lifecyclehandler-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">LifecycleHandler</span> <span class="v">v1</span> <span class="g">core</span></span></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>LifecycleHandler</CODE></TD></TR>
</TBODY>
</TABLE>
<P>LifecycleHandler defines a specific action that should be taken in a lifecycle hook. One and only one of the fields, except TCPSocket must be specified.</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>Exec specifies a command to execute in the container.</TD></TR>
<TR><TD><CODE>httpGet</CODE><BR /><I><a href="#httpgetaction-v1-core">HTTPGetAction</a></I></TD><TD>HTTPGet specifies an HTTP GET request to perform.</TD></TR>
<TR><TD><CODE>sleep</CODE><BR /><I><a href="#sleepaction-v1-core">SleepAction</a></I></TD><TD>Sleep represents a duration that the container should sleep.</TD></TR>
<TR><TD><CODE>tcpSocket</CODE><BR /><I><a href="#tcpsocketaction-v1-core">TCPSocketAction</a></I></TD><TD>Deprecated. TCPSocket is NOT supported as a LifecycleHandler and kept for backward compatibility. There is no validation of this field and lifecycle hooks will fail at runtime when it is specified.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="limitrangeitem-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">LimitRangeItem</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="limitresponse-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">LimitResponse</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LimitResponse</CODE></TD></TR>
</TBODY>
</TABLE>
<P>LimitResponse defines how to handle requests that can not be executed right now.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#limitedprioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">LimitedPriorityLevelConfiguration [flowcontrol/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>queuing</CODE><BR /><I><a href="#queuingconfiguration-v1-flowcontrol-apiserver-k8s-io">QueuingConfiguration</a></I></TD><TD>`queuing` holds the configuration parameters for queuing. This field may be non-empty only if `type` is `&#34;Queue&#34;`.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is &#34;Queue&#34; or &#34;Reject&#34;. &#34;Queue&#34; means that requests that can not be executed upon arrival are held in a queue until they can be executed or a queuing limit is reached. &#34;Reject&#34; means that requests that can not be executed upon arrival are rejected. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="limitedprioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">LimitedPriorityLevelConfiguration</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LimitedPriorityLevelConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<P>LimitedPriorityLevelConfiguration specifies how to handle requests that are subject to limits. It addresses two issues:
- How are requests for this priority level limited?
- What should be done with requests that exceed the limit?</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#prioritylevelconfigurationspec-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationSpec [flowcontrol/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>borrowingLimitPercent</CODE><BR /><I>integer</I></TD><TD>`borrowingLimitPercent`, if present, configures a limit on how many seats this priority level can borrow from other priority levels. The limit is known as this level&#39;s BorrowingConcurrencyLimit (BorrowingCL) and is a limit on the total number of seats that this level may borrow at any one time. This field holds the ratio of that limit to the level&#39;s nominal concurrency limit. When this field is non-nil, it must hold a non-negative integer and the limit is calculated as follows. BorrowingCL(i) = round( NominalCL(i) * borrowingLimitPercent(i)/100.0 ) The value of this field can be more than 100, implying that this priority level can borrow a number of seats that is greater than its own nominal concurrency limit (NominalCL). When this field is left `nil`, the limit is effectively infinite.</TD></TR>
<TR><TD><CODE>lendablePercent</CODE><BR /><I>integer</I></TD><TD>`lendablePercent` prescribes the fraction of the level&#39;s NominalCL that can be borrowed by other priority levels. The value of this field must be between 0 and 100, inclusive, and it defaults to 0. The number of seats that other levels can borrow from this level, known as this level&#39;s LendableConcurrencyLimit (LendableCL), is defined as follows. LendableCL(i) = round( NominalCL(i) * lendablePercent(i)/100.0 )</TD></TR>
<TR><TD><CODE>limitResponse</CODE><BR /><I><a href="#limitresponse-v1-flowcontrol-apiserver-k8s-io">LimitResponse</a></I></TD><TD>`limitResponse` indicates what to do with requests that can not be executed right now</TD></TR>
<TR><TD><CODE>nominalConcurrencyShares</CODE><BR /><I>integer</I></TD><TD>`nominalConcurrencyShares` (NCS) contributes to the computation of the NominalConcurrencyLimit (NominalCL) of this level. This is the number of execution seats available at this priority level. This is used both for requests dispatched from this priority level as well as requests dispatched from other priority levels borrowing seats from this level. The server&#39;s concurrency limit (ServerCL) is divided among the Limited priority levels in proportion to their NCS values: NominalCL(i) = ceil( ServerCL * NCS(i) / sum_ncs ) sum_ncs = sum[priority level k] NCS(k) Bigger numbers mean a larger nominal concurrency limit, at the expense of every other priority level. If not specified, this field defaults to a value of 30. Setting this field to zero supports the construction of a &#34;jail&#34; for this priority level that is used to hold some request(s)</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="linuxcontaineruser-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">LinuxContainerUser</span> <span class="v">v1</span> <span class="g">core</span></span></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>LinuxContainerUser</CODE></TD></TR>
</TBODY>
</TABLE>
<P>LinuxContainerUser represents user identity information in Linux containers</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#containeruser-v1-core">ContainerUser [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>gid</CODE><BR /><I>integer</I></TD><TD>GID is the primary gid initially attached to the first process in the container</TD></TR>
<TR><TD><CODE>supplementalGroups</CODE><BR /><I>integer array</I></TD><TD>SupplementalGroups are the supplemental groups initially attached to the first process in the container</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>integer</I></TD><TD>UID is the primary uid initially attached to the first process in the container</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="listmeta-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">ListMeta</span> <span class="v">v1</span> <span class="g">meta</span></span></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="#csidriverlist-v1-storage-k8s-io">CSIDriverList [storage/v1]</a></LI>
<LI><a href="#csinodelist-v1-storage-k8s-io">CSINodeList [storage/v1]</a></LI>
<LI><a href="#csistoragecapacitylist-v1-storage-k8s-io">CSIStorageCapacityList [storage/v1]</a></LI>
<LI><a href="#certificatesigningrequestlist-v1-certificates-k8s-io">CertificateSigningRequestList [certificates/v1]</a></LI>
<LI><a href="#clusterrolebindinglist-v1-rbac-authorization-k8s-io">ClusterRoleBindingList [rbac/v1]</a></LI>
<LI><a href="#clusterrolelist-v1-rbac-authorization-k8s-io">ClusterRoleList [rbac/v1]</a></LI>
<LI><a href="#clustertrustbundlelist-v1alpha1-certificates-k8s-io">ClusterTrustBundleList [certificates/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="#cronjoblist-v1-batch">CronJobList [batch/v1]</a></LI>
<LI><a href="#customresourcedefinitionlist-v1-apiextensions-k8s-io">CustomResourceDefinitionList [apiextensions/v1]</a></LI>
<LI><a href="#daemonsetlist-v1-apps">DaemonSetList [apps/v1]</a></LI>
<LI><a href="#deploymentlist-v1-apps">DeploymentList [apps/v1]</a></LI>
<LI><a href="#deviceclasslist-v1beta1-resource-k8s-io">DeviceClassList [resource/v1beta1]</a></LI>
<LI><a href="#deviceclasslist-v1alpha3-resource-k8s-io">DeviceClassList [resource/v1alpha3]</a></LI>
<LI><a href="#endpointslicelist-v1-discovery-k8s-io">EndpointSliceList [discovery/v1]</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-v1-events-k8s-io">EventList [events/v1]</a></LI>
<LI><a href="#flowschemalist-v1-flowcontrol-apiserver-k8s-io">FlowSchemaList [flowcontrol/v1]</a></LI>
<LI><a href="#horizontalpodautoscalerlist-v2-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2]</a></LI>
<LI><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v1]</a></LI>
<LI><a href="#ipaddresslist-v1beta1-networking-k8s-io">IPAddressList [networking/v1beta1]</a></LI>
<LI><a href="#ingressclasslist-v1-networking-k8s-io">IngressClassList [networking/v1]</a></LI>
<LI><a href="#ingresslist-v1-networking-k8s-io">IngressList [networking/v1]</a></LI>
<LI><a href="#joblist-v1-batch">JobList [batch/v1]</a></LI>
<LI><a href="#leasecandidatelist-v1alpha2-coordination-k8s-io">LeaseCandidateList [coordination/v1alpha2]</a></LI>
<LI><a href="#leaselist-v1-coordination-k8s-io">LeaseList [coordination/v1]</a></LI>
<LI><a href="#limitrangelist-v1-core">LimitRangeList [core/v1]</a></LI>
<LI><a href="#mutatingadmissionpolicybindinglist-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBindingList [admissionregistration/v1alpha1]</a></LI>
<LI><a href="#mutatingadmissionpolicylist-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyList [admissionregistration/v1alpha1]</a></LI>
<LI><a href="#mutatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">MutatingWebhookConfigurationList [admissionregistration/v1]</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="#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-v1-policy">PodDisruptionBudgetList [policy/v1]</a></LI>
<LI><a href="#podlist-v1-core">PodList [core/v1]</a></LI>
<LI><a href="#podtemplatelist-v1-core">PodTemplateList [core/v1]</a></LI>
<LI><a href="#priorityclasslist-v1-scheduling-k8s-io">PriorityClassList [scheduling/v1]</a></LI>
<LI><a href="#prioritylevelconfigurationlist-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationList [flowcontrol/v1]</a></LI>
<LI><a href="#replicasetlist-v1-apps">ReplicaSetList [apps/v1]</a></LI>
<LI><a href="#replicationcontrollerlist-v1-core">ReplicationControllerList [core/v1]</a></LI>
<LI><a href="#resourceclaimlist-v1beta1-resource-k8s-io">ResourceClaimList [resource/v1beta1]</a></LI>
<LI><a href="#resourceclaimlist-v1alpha3-resource-k8s-io">ResourceClaimList [resource/v1alpha3]</a></LI>
<LI><a href="#resourceclaimtemplatelist-v1beta1-resource-k8s-io">ResourceClaimTemplateList [resource/v1beta1]</a></LI>
<LI><a href="#resourceclaimtemplatelist-v1alpha3-resource-k8s-io">ResourceClaimTemplateList [resource/v1alpha3]</a></LI>
<LI><a href="#resourcequotalist-v1-core">ResourceQuotaList [core/v1]</a></LI>
<LI><a href="#resourceslicelist-v1beta1-resource-k8s-io">ResourceSliceList [resource/v1beta1]</a></LI>
<LI><a href="#resourceslicelist-v1alpha3-resource-k8s-io">ResourceSliceList [resource/v1alpha3]</a></LI>
<LI><a href="#rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList [rbac/v1]</a></LI>
<LI><a href="#rolelist-v1-rbac-authorization-k8s-io">RoleList [rbac/v1]</a></LI>
<LI><a href="#runtimeclasslist-v1-node-k8s-io">RuntimeClassList [node/v1]</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="#servicecidrlist-v1beta1-networking-k8s-io">ServiceCIDRList [networking/v1beta1]</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="#status-v1-meta">Status [meta/v1]</a></LI>
<LI><a href="#storageclasslist-v1-storage-k8s-io">StorageClassList [storage/v1]</a></LI>
<LI><a href="#storageversionlist-v1alpha1-internal-apiserver-k8s-io">StorageVersionList [apiserverinternal/v1alpha1]</a></LI>
<LI><a href="#storageversionmigrationlist-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationList [storagemigration/v1alpha1]</a></LI>
<LI><a href="#validatingadmissionpolicybindinglist-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList [admissionregistration/v1]</a></LI>
<LI><a href="#validatingadmissionpolicybindinglist-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList [admissionregistration/v1beta1]</a></LI>
<LI><a href="#validatingadmissionpolicylist-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList [admissionregistration/v1]</a></LI>
<LI><a href="#validatingadmissionpolicylist-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList [admissionregistration/v1beta1]</a></LI>
<LI><a href="#validatingwebhookconfigurationlist-v1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList [admissionregistration/v1]</a></LI>
<LI><a href="#volumeattachmentlist-v1-storage-k8s-io">VolumeAttachmentList [storage/v1]</a></LI>
<LI><a href="#volumeattributesclasslist-v1beta1-storage-k8s-io">VolumeAttributesClassList [storage/v1beta1]</a></LI>
<LI><a href="#volumeattributesclasslist-v1alpha1-storage-k8s-io">VolumeAttributesClassList [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 consistent 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, unless you have received this token from an error message.</TD></TR>
<TR><TD><CODE>remainingItemCount</CODE><BR /><I>integer</I></TD><TD>remainingItemCount is the number of subsequent items in the list which are not included in this list response. If the list request contained label or field selectors, then the number of remaining items is unknown and the field will be left unset and omitted during serialization. If the list is complete (either because it is not chunking or because this is the last chunk), then there are no more remaining items and this field will be left unset and omitted during serialization. Servers older than v1.15 do not set this field. The intended use of the remainingItemCount is *estimating* the size of a collection. Clients should not rely on the remainingItemCount to be set or to be exact.</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/sig-architecture/api-conventions.md#concurrency-control-and-consistency</TD></TR>
<TR><TD><CODE>selfLink</CODE><BR /><I>string</I></TD><TD>Deprecated: selfLink is a legacy read-only field that is no longer populated by the system.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="loadbalanceringress-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">LoadBalancerIngress</span> <span class="v">v1</span> <span class="g">core</span></span></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>
<TR><TD><CODE>ipMode</CODE><BR /><I>string</I></TD><TD>IPMode specifies how the load-balancer IP behaves, and may only be specified when the ip field is specified. Setting this to &#34;VIP&#34; indicates that traffic is delivered to the node with the destination set to the load-balancer&#39;s IP and port. Setting this to &#34;Proxy&#34; indicates that traffic is delivered to the node or pod with the destination set to the node&#39;s IP and node port or the pod&#39;s IP and port. Service implementations may use this information to adjust traffic routing.</TD></TR>
<TR><TD><CODE>ports</CODE><BR /><I><a href="#portstatus-v1-core">PortStatus</a> array</I></TD><TD>Ports is a list of records of service ports If used, every port defined in the service should have an entry in it</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="loadbalancerstatus-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">LoadBalancerStatus</span> <span class="v">v1</span> <span class="g">core</span></span></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="#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>
</DIV>
<DIV class="definition-container" id="localobjectreference-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">LocalObjectReference</span> <span class="v">v1</span> <span class="g">core</span></span></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="#csivolumesource-v1-core">CSIVolumeSource [core/v1]</a></LI>
<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. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="localvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">LocalVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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</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>fsType is the filesystem type to mount. It applies only when the Path is a block device. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. The default value is to auto-select a filesystem if unspecified.</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>path of the full path to the volume on the node. It can be either a directory or block device (disk, partition, ...).</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="managedfieldsentry-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">ManagedFieldsEntry</span> <span class="v">v1</span> <span class="g">meta</span></span></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>ManagedFieldsEntry</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ManagedFieldsEntry is a workflow-id, a FieldSet and the group version of the resource that the fieldset applies to.</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>APIVersion defines the version of this resource that this field set applies to. The format is &#34;group/version&#34; just like the top-level APIVersion field. It is necessary to track the version of a field set because it cannot be automatically converted.</TD></TR>
<TR><TD><CODE>fieldsType</CODE><BR /><I>string</I></TD><TD>FieldsType is the discriminator for the different fields format and version. There is currently only one possible value: &#34;FieldsV1&#34;</TD></TR>
<TR><TD><CODE>fieldsV1</CODE><BR /><I><a href="#fieldsv1-v1-meta">FieldsV1</a></I></TD><TD>FieldsV1 holds the first JSON version format as described in the &#34;FieldsV1&#34; type.</TD></TR>
<TR><TD><CODE>manager</CODE><BR /><I>string</I></TD><TD>Manager is an identifier of the workflow managing these fields.</TD></TR>
<TR><TD><CODE>operation</CODE><BR /><I>string</I></TD><TD>Operation is the type of operation which lead to this ManagedFieldsEntry being created. The only valid values for this field are &#39;Apply&#39; and &#39;Update&#39;.</TD></TR>
<TR><TD><CODE>subresource</CODE><BR /><I>string</I></TD><TD>Subresource is the name of the subresource used to update that object, or empty string if the object was updated through the main resource. The value of this field is used to distinguish between managers, even if they share the same name. For example, a status update will be distinct from a regular update using the same manager name. Note that the APIVersion field is not related to the Subresource field and it always corresponds to the version of the main resource.</TD></TR>
<TR><TD><CODE>time</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time is the timestamp of when the ManagedFields entry was added. The timestamp will also be updated if a field is added, the manager changes any of the owned fields value or removes a field. The timestamp does not update when a field is removed from the entry because another manager took it over.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="matchcondition-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">MatchCondition</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>MatchCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>MatchCondition represents a condition which must by fulfilled for a request to be sent to a webhook.</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="#matchcondition-v1beta1-admissionregistration-k8s-io">v1beta1</a>
<a href="#matchcondition-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="#mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook [admissionregistration/v1]</a></LI>
<LI><a href="#validatingadmissionpolicyspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1]</a></LI>
<LI><a href="#validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables: &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. &#39;request&#39; - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request. See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the request resource. Documentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/ Required.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;, and must start and end with an alphanumeric character (e.g. &#39;MyName&#39;, or &#39;my.name&#39;, or &#39;123-abc&#39;, regex used for validation is &#39;([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]&#39;) with an optional DNS subdomain prefix and &#39;/&#39; (e.g. &#39;example.com/MyName&#39;) Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="matchresources-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">MatchResources</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>MatchResources</CODE></TD></TR>
</TBODY>
</TABLE>
<P>MatchResources decides whether to run the admission control policy on an object based on whether it meets the match criteria. The exclude rules take precedence over include rules (if a resource matches both, it is excluded)</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="#matchresources-v1beta1-admissionregistration-k8s-io">v1beta1</a>
<a href="#matchresources-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="#validatingadmissionpolicybindingspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec [admissionregistration/v1]</a></LI>
<LI><a href="#validatingadmissionpolicyspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>excludeResourceRules</CODE><BR /><I><a href="#namedrulewithoperations-v1-admissionregistration-k8s-io">NamedRuleWithOperations</a> array</I></TD><TD>ExcludeResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy should not care about. The exclude rules take precedence over include rules (if a resource matches both, it is excluded)</TD></TR>
<TR><TD><CODE>matchPolicy</CODE><BR /><I>string</I></TD><TD>matchPolicy defines how the &#34;MatchResources&#34; list is used to match incoming requests. Allowed values are &#34;Exact&#34; or &#34;Equivalent&#34;. - Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the ValidatingAdmissionPolicy. - Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the ValidatingAdmissionPolicy. Defaults to &#34;Equivalent&#34;</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 admission control policy 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 policy. 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 policy 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>objectSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>ObjectSelector decides whether to run the validation based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the cel validation, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.</TD></TR>
<TR><TD><CODE>resourceRules</CODE><BR /><I><a href="#namedrulewithoperations-v1-admissionregistration-k8s-io">NamedRuleWithOperations</a> array</I></TD><TD>ResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy matches. The policy cares about an operation if it matches _any_ Rule.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="metricidentifier-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">MetricIdentifier</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</CODE></TD><TD><CODE>MetricIdentifier</CODE></TD></TR>
</TBODY>
</TABLE>
<P>MetricIdentifier defines the name and optionally selector for a metric</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#externalmetricsource-v2-autoscaling">ExternalMetricSource [autoscaling/v2]</a></LI>
<LI><a href="#externalmetricstatus-v2-autoscaling">ExternalMetricStatus [autoscaling/v2]</a></LI>
<LI><a href="#objectmetricsource-v2-autoscaling">ObjectMetricSource [autoscaling/v2]</a></LI>
<LI><a href="#objectmetricstatus-v2-autoscaling">ObjectMetricStatus [autoscaling/v2]</a></LI>
<LI><a href="#podsmetricsource-v2-autoscaling">PodsMetricSource [autoscaling/v2]</a></LI>
<LI><a href="#podsmetricstatus-v2-autoscaling">PodsMetricStatus [autoscaling/v2]</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 given metric</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is the string-encoded form of a standard kubernetes label selector for the given metric When set, it is passed as an additional parameter to the metrics server for more specific metrics scoping. When unset, just the metricName will be used to gather metrics.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="metricspec-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">MetricSpec</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>containerResource</CODE><BR /><I><a href="#containerresourcemetricsource-v2-autoscaling">ContainerResourceMetricSource</a></I></TD><TD>containerResource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in each pod of 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>external</CODE><BR /><I><a href="#externalmetricsource-v2-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-v2-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-v2-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-v2-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;ContainerResource&#34;, &#34;External&#34;, &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each mapping to a matching field in the object.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="metricstatus-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">MetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>containerResource</CODE><BR /><I><a href="#containerresourcemetricstatus-v2-autoscaling">ContainerResourceMetricStatus</a></I></TD><TD>container resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing a single container in 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>external</CODE><BR /><I><a href="#externalmetricstatus-v2-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-v2-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-v2-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-v2-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;ContainerResource&#34;, &#34;External&#34;, &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each corresponds to a matching field in the object.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="metrictarget-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">MetricTarget</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</CODE></TD><TD><CODE>MetricTarget</CODE></TD></TR>
</TBODY>
</TABLE>
<P>MetricTarget defines the target value, average value, or average utilization of a specific metric</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#containerresourcemetricsource-v2-autoscaling">ContainerResourceMetricSource [autoscaling/v2]</a></LI>
<LI><a href="#externalmetricsource-v2-autoscaling">ExternalMetricSource [autoscaling/v2]</a></LI>
<LI><a href="#objectmetricsource-v2-autoscaling">ObjectMetricSource [autoscaling/v2]</a></LI>
<LI><a href="#podsmetricsource-v2-autoscaling">PodsMetricSource [autoscaling/v2]</a></LI>
<LI><a href="#resourcemetricsource-v2-autoscaling">ResourceMetricSource [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>averageUtilization</CODE><BR /><I>integer</I></TD><TD>averageUtilization 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. Currently only valid for Resource metric source type</TD></TR>
<TR><TD><CODE>averageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>averageValue is the target value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type represents whether the metric type is Utilization, Value, or AverageValue</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>value is the target value of the metric (as a quantity).</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="metricvaluestatus-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">MetricValueStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</CODE></TD><TD><CODE>MetricValueStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>MetricValueStatus holds the current value for a metric</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#containerresourcemetricstatus-v2-autoscaling">ContainerResourceMetricStatus [autoscaling/v2]</a></LI>
<LI><a href="#externalmetricstatus-v2-autoscaling">ExternalMetricStatus [autoscaling/v2]</a></LI>
<LI><a href="#objectmetricstatus-v2-autoscaling">ObjectMetricStatus [autoscaling/v2]</a></LI>
<LI><a href="#podsmetricstatus-v2-autoscaling">PodsMetricStatus [autoscaling/v2]</a></LI>
<LI><a href="#resourcemetricstatus-v2-autoscaling">ResourceMetricStatus [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>averageUtilization</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.</TD></TR>
<TR><TD><CODE>averageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>averageValue is the current value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>value is the current value of the metric (as a quantity).</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="microtime-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">MicroTime</span> <span class="v">v1</span> <span class="g">meta</span></span></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-v1-events-k8s-io">Event [events/v1]</a></LI>
<LI><a href="#eventseries-v1-core">EventSeries [core/v1]</a></LI>
<LI><a href="#eventseries-v1-events-k8s-io">EventSeries [events/v1]</a></LI>
<LI><a href="#leasecandidatespec-v1alpha2-coordination-k8s-io">LeaseCandidateSpec [coordination/v1alpha2]</a></LI>
<LI><a href="#leasespec-v1-coordination-k8s-io">LeaseSpec [coordination/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="migrationcondition-v1alpha1-storagemigration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">MigrationCondition</span> <span class="v">v1alpha1</span> <span class="g">storagemigration.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storagemigration.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>MigrationCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Describes the state of a migration 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="#storageversionmigrationstatus-v1alpha1-storagemigration-k8s-io">StorageVersionMigrationStatus [storagemigration/v1alpha1]</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>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 the condition.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="modifyvolumestatus-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ModifyVolumeStatus</span> <span class="v">v1</span> <span class="g">core</span></span></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>ModifyVolumeStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ModifyVolumeStatus represents the status object of ControllerModifyVolume operation</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>status</CODE><BR /><I>string</I></TD><TD>status is the status of the ControllerModifyVolume operation. It can be in any of following states: - Pending Pending indicates that the PersistentVolumeClaim cannot be modified due to unmet requirements, such as the specified VolumeAttributesClass not existing. - InProgress InProgress indicates that the volume is being modified. - Infeasible Infeasible indicates that the request has been rejected as invalid by the CSI driver. To resolve the error, a valid VolumeAttributesClass needs to be specified. Note: New statuses can be added in the future. Consumers should check for unknown statuses and fail appropriately.</TD></TR>
<TR><TD><CODE>targetVolumeAttributesClassName</CODE><BR /><I>string</I></TD><TD>targetVolumeAttributesClassName is the name of the VolumeAttributesClass the PVC currently being reconciled</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="mutatingwebhook-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">MutatingWebhook</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>MutatingWebhook</CODE></TD></TR>
</TBODY>
</TABLE>
<P>MutatingWebhook 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-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionReviewVersions</CODE><BR /><I>string array</I></TD><TD>AdmissionReviewVersions is an ordered list of preferred `AdmissionReview` versions the Webhook expects. API server will try to use first version in the list which it supports. If none of the versions specified in this list supported by API server, validation will fail for this object. If a persisted webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail and be subject to the failure policy.</TD></TR>
<TR><TD><CODE>clientConfig</CODE><BR /><I><a href="#webhookclientconfig-v1-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 Fail.</TD></TR>
<TR><TD><CODE>matchConditions</CODE><BR /><I><a href="#matchcondition-v1-admissionregistration-k8s-io">MatchCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>MatchConditions is a list of conditions that must be met for a request to be sent to this webhook. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed. The exact matching logic is (in order): 1. If ANY matchCondition evaluates to FALSE, the webhook is skipped. 2. If ALL matchConditions evaluate to TRUE, the webhook is called. 3. If any matchCondition evaluates to an error (but none are FALSE): - If failurePolicy=Fail, reject the request - If failurePolicy=Ignore, the error is ignored and the webhook is skipped</TD></TR>
<TR><TD><CODE>matchPolicy</CODE><BR /><I>string</I></TD><TD>matchPolicy defines how the &#34;rules&#34; list is used to match incoming requests. Allowed values are &#34;Exact&#34; or &#34;Equivalent&#34;. - Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook. - Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook. Defaults to &#34;Equivalent&#34;</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>objectSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>ObjectSelector decides whether to run the webhook based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the webhook, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.</TD></TR>
<TR><TD><CODE>reinvocationPolicy</CODE><BR /><I>string</I></TD><TD>reinvocationPolicy indicates whether this webhook should be called multiple times as part of a single admission evaluation. Allowed values are &#34;Never&#34; and &#34;IfNeeded&#34;. Never: the webhook will not be called more than once in a single admission evaluation. IfNeeded: the webhook will be called at least one additional time as part of the admission evaluation if the object being admitted is modified by other admission plugins after the initial webhook call. Webhooks that specify this option *must* be idempotent, able to process objects they previously admitted. Note: * the number of additional invocations is not guaranteed to be exactly one. * if additional invocations result in further modifications to the object, webhooks are not guaranteed to be invoked again. * webhooks that use this option may be reordered to minimize the number of additional invocations. * to validate an object after all mutations are guaranteed complete, use a validating admission webhook instead. Defaults to &#34;Never&#34;.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#rulewithoperations-v1-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>
<TR><TD><CODE>sideEffects</CODE><BR /><I>string</I></TD><TD>SideEffects states whether this webhook has side effects. Acceptable values are: None, NoneOnDryRun (webhooks created via v1beta1 may also specify Some or Unknown). Webhooks with side effects MUST implement a reconciliation system, since a request may be rejected by a future step in the admission chain and the side effects therefore need to be undone. Requests with the dryRun attribute will be auto-rejected if they match a webhook with sideEffects == Unknown or Some.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE><BR /><I>integer</I></TD><TD>TimeoutSeconds specifies the timeout for this webhook. After the timeout passes, the webhook call will be ignored or the API call will fail based on the failure policy. The timeout value must be between 1 and 30 seconds. Default to 10 seconds.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="mutation-v1alpha1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">Mutation</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>Mutation</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Mutation specifies the CEL expression which is used to apply the Mutation.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#mutatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicySpec [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>applyConfiguration</CODE><BR /><I><a href="#applyconfiguration-v1alpha1-admissionregistration-k8s-io">ApplyConfiguration</a></I></TD><TD>applyConfiguration defines the desired configuration values of an object. The configuration is applied to the admission object using [structured merge diff](https://github.com/kubernetes-sigs/structured-merge-diff). A CEL expression is used to create apply configuration.</TD></TR>
<TR><TD><CODE>jsonPatch</CODE><BR /><I><a href="#jsonpatch-v1alpha1-admissionregistration-k8s-io">JSONPatch</a></I></TD><TD>jsonPatch defines a [JSON patch](https://jsonpatch.com/) operation to perform a mutation to the object. A CEL expression is used to create the JSON patch.</TD></TR>
<TR><TD><CODE>patchType</CODE><BR /><I>string</I></TD><TD>patchType indicates the patch strategy used. Allowed values are &#34;ApplyConfiguration&#34; and &#34;JSONPatch&#34;. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="nfsvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NFSVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="namedrulewithoperations-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">NamedRuleWithOperations</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>NamedRuleWithOperations</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NamedRuleWithOperations is a tuple of Operations and Resources with ResourceNames.</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="#namedrulewithoperations-v1beta1-admissionregistration-k8s-io">v1beta1</a>
<a href="#namedrulewithoperations-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="#matchresources-v1-admissionregistration-k8s-io">MatchResources [admissionregistration/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 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, DELETE, CONNECT or * for all of those operations and any future admission operations that are added. If &#39;\*&#39; is present, the length of the slice must be one. Required.</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. 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>
<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>scope specifies the scope of this rule. Valid values are &#34;Cluster&#34;, &#34;Namespaced&#34;, and &#34;*&#34; &#34;Cluster&#34; means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. &#34;Namespaced&#34; means that only namespaced resources will match this rule. &#34;*&#34; means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is &#34;*&#34;.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="namespacecondition-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NamespaceCondition</span> <span class="v">v1</span> <span class="g">core</span></span></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>NamespaceCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NamespaceCondition contains details about state of namespace.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#namespacestatus-v1-core">NamespaceStatus [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>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 of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of namespace controller condition.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="networkdevicedata-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">NetworkDeviceData</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>NetworkDeviceData</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NetworkDeviceData provides network-related details for the allocated device. This information may be filled by drivers or other components to configure or identify the device within a network context.</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="#networkdevicedata-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#allocateddevicestatus-v1beta1-resource-k8s-io">AllocatedDeviceStatus [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>hardwareAddress</CODE><BR /><I>string</I></TD><TD>HardwareAddress represents the hardware address (e.g. MAC Address) of the device&#39;s network interface. Must not be longer than 128 characters.</TD></TR>
<TR><TD><CODE>interfaceName</CODE><BR /><I>string</I></TD><TD>InterfaceName specifies the name of the network interface associated with the allocated device. This might be the name of a physical or virtual network interface being configured in the pod. Must not be longer than 256 characters.</TD></TR>
<TR><TD><CODE>ips</CODE><BR /><I>string array</I></TD><TD>IPs lists the network addresses assigned to the device&#39;s network interface. This can include both IPv4 and IPv6 addresses. The IPs are in the CIDR notation, which includes both the address and the associated subnet mask. e.g.: &#34;192.0.2.5/24&#34; for IPv4 and &#34;2001:db8::5/64&#34; for IPv6.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="networkpolicyegressrule-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">NetworkPolicyEgressRule</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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-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>ports is a 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>to is a 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>
</DIV>
<DIV class="definition-container" id="networkpolicyingressrule-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">NetworkPolicyIngressRule</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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-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>from is a 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 one 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>ports is a 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>
</DIV>
<DIV class="definition-container" id="networkpolicypeer-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">NetworkPolicyPeer</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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 to/from. Only certain combinations of fields are allowed</P>
<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>namespaceSelector 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>podSelector 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>
</DIV>
<DIV class="definition-container" id="networkpolicyport-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">NetworkPolicyPort</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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-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>endPort</CODE><BR /><I>integer</I></TD><TD>endPort indicates that the range of ports from port to endPort if set, inclusive, should be allowed by the policy. This field cannot be defined if the port field is not defined or if the port field is defined as a named (string) port. The endPort must be equal or greater than port.</TD></TR>
<TR><TD><CODE>port</CODE></TD><TD>port represents 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>protocol represents the protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this field defaults to TCP.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="nodeaddress-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeAddress</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="nodeaffinity-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeAffinity</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="nodecondition-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeCondition</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="nodeconfigsource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeConfigSource</span> <span class="v">v1</span> <span class="g">core</span></span></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. This API is deprecated since 1.22</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>
</DIV>
<DIV class="definition-container" id="nodeconfigstatus-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeConfigStatus</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="nodedaemonendpoints-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeDaemonEndpoints</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="nodefeatures-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeFeatures</span> <span class="v">v1</span> <span class="g">core</span></span></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>NodeFeatures</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NodeFeatures describes the set of features implemented by the CRI implementation. The features contained in the NodeFeatures should depend only on the cri implementation independent of runtime handlers.</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>supplementalGroupsPolicy</CODE><BR /><I>boolean</I></TD><TD>SupplementalGroupsPolicy is set to true if the runtime supports SupplementalGroupsPolicy and ContainerUser.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="noderuntimehandler-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeRuntimeHandler</span> <span class="v">v1</span> <span class="g">core</span></span></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>NodeRuntimeHandler</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NodeRuntimeHandler is a set of runtime handler information.</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>features</CODE><BR /><I><a href="#noderuntimehandlerfeatures-v1-core">NodeRuntimeHandlerFeatures</a></I></TD><TD>Supported features.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Runtime handler name. Empty for the default runtime handler.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="noderuntimehandlerfeatures-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeRuntimeHandlerFeatures</span> <span class="v">v1</span> <span class="g">core</span></span></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>NodeRuntimeHandlerFeatures</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NodeRuntimeHandlerFeatures is a set of features implemented by the runtime handler.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#noderuntimehandler-v1-core">NodeRuntimeHandler [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>recursiveReadOnlyMounts</CODE><BR /><I>boolean</I></TD><TD>RecursiveReadOnlyMounts is set to true if the runtime handler supports RecursiveReadOnlyMounts.</TD></TR>
<TR><TD><CODE>userNamespaces</CODE><BR /><I>boolean</I></TD><TD>UserNamespaces is set to true if the runtime handler supports UserNamespaces, including for volumes.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="nodeselector-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeSelector</span> <span class="v">v1</span> <span class="g">core</span></span></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="#allocationresult-v1beta1-resource-k8s-io">AllocationResult [resource/v1beta1]</a></LI>
<LI><a href="#allocationresult-v1alpha3-resource-k8s-io">AllocationResult [resource/v1alpha3]</a></LI>
<LI><a href="#nodeaffinity-v1-core">NodeAffinity [core/v1]</a></LI>
<LI><a href="#resourceslicespec-v1beta1-resource-k8s-io">ResourceSliceSpec [resource/v1beta1]</a></LI>
<LI><a href="#resourceslicespec-v1alpha3-resource-k8s-io">ResourceSliceSpec [resource/v1alpha3]</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>
</DIV>
<DIV class="definition-container" id="nodeselectorrequirement-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeSelectorRequirement</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="nodeselectorterm-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeSelectorTerm</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="nodesysteminfo-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">NodeSystemInfo</span> <span class="v">v1</span> <span class="g">core</span></span></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. containerd://1.4.2).</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>Deprecated: 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/uuid</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="nonresourceattributes-v1-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">NonResourceAttributes</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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-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>
</DIV>
<DIV class="definition-container" id="nonresourcepolicyrule-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">NonResourcePolicyRule</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NonResourcePolicyRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NonResourcePolicyRule is a predicate that matches non-resource requests according to their verb and the target non-resource URL. A NonResourcePolicyRule matches a request if and only if both (a) at least one member of verbs matches the request and (b) at least one member of nonResourceURLs matches the request.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#policyruleswithsubjects-v1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/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 url prefixes that a user should have access to and may not be empty. For example: - &#34;/healthz&#34; is legal - &#34;/hea*&#34; is illegal - &#34;/hea&#34; is legal but matches nothing - &#34;/hea/*&#34; also matches nothing - &#34;/healthz/*&#34; matches all per-component health checks. &#34;*&#34; matches all non-resource urls. if it is present, it must be the only entry. Required.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>`verbs` is a list of matching verbs and may not be empty. &#34;*&#34; matches all verbs. If it is present, it must be the only entry. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="nonresourcerule-v1-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">NonResourceRule</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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-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>
</DIV>
<DIV class="definition-container" id="objectfieldselector-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ObjectFieldSelector</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="objectmeta-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">ObjectMeta</span> <span class="v">v1</span> <span class="g">meta</span></span></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="#binding-v1-core">Binding [core/v1]</a></LI>
<LI><a href="#csidriver-v1-storage-k8s-io">CSIDriver [storage/v1]</a></LI>
<LI><a href="#csinode-v1-storage-k8s-io">CSINode [storage/v1]</a></LI>
<LI><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity [storage/v1]</a></LI>
<LI><a href="#certificatesigningrequest-v1-certificates-k8s-io">CertificateSigningRequest [certificates/v1]</a></LI>
<LI><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole [rbac/v1]</a></LI>
<LI><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1]</a></LI>
<LI><a href="#clustertrustbundle-v1alpha1-certificates-k8s-io">ClusterTrustBundle [certificates/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="#cronjob-v1-batch">CronJob [batch/v1]</a></LI>
<LI><a href="#customresourcedefinition-v1-apiextensions-k8s-io">CustomResourceDefinition [apiextensions/v1]</a></LI>
<LI><a href="#daemonset-v1-apps">DaemonSet [apps/v1]</a></LI>
<LI><a href="#deployment-v1-apps">Deployment [apps/v1]</a></LI>
<LI><a href="#deviceclass-v1beta1-resource-k8s-io">DeviceClass [resource/v1beta1]</a></LI>
<LI><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass [resource/v1alpha3]</a></LI>
<LI><a href="#endpointslice-v1-discovery-k8s-io">EndpointSlice [discovery/v1]</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-v1-events-k8s-io">Event [events/v1]</a></LI>
<LI><a href="#eviction-v1-policy">Eviction [policy/v1]</a></LI>
<LI><a href="#flowschema-v1-flowcontrol-apiserver-k8s-io">FlowSchema [flowcontrol/v1]</a></LI>
<LI><a href="#horizontalpodautoscaler-v2-autoscaling">HorizontalPodAutoscaler [autoscaling/v2]</a></LI>
<LI><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler [autoscaling/v1]</a></LI>
<LI><a href="#ipaddress-v1beta1-networking-k8s-io">IPAddress [networking/v1beta1]</a></LI>
<LI><a href="#ingress-v1-networking-k8s-io">Ingress [networking/v1]</a></LI>
<LI><a href="#ingressclass-v1-networking-k8s-io">IngressClass [networking/v1]</a></LI>
<LI><a href="#job-v1-batch">Job [batch/v1]</a></LI>
<LI><a href="#jobtemplatespec-v1-batch">JobTemplateSpec [batch/v1]</a></LI>
<LI><a href="#lease-v1-coordination-k8s-io">Lease [coordination/v1]</a></LI>
<LI><a href="#leasecandidate-v1alpha2-coordination-k8s-io">LeaseCandidate [coordination/v1alpha2]</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="#mutatingadmissionpolicy-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicy [admissionregistration/v1alpha1]</a></LI>
<LI><a href="#mutatingadmissionpolicybinding-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBinding [admissionregistration/v1alpha1]</a></LI>
<LI><a href="#mutatingwebhookconfiguration-v1-admissionregistration-k8s-io">MutatingWebhookConfiguration [admissionregistration/v1]</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="#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="#persistentvolumeclaimtemplate-v1-core">PersistentVolumeClaimTemplate [core/v1]</a></LI>
<LI><a href="#pod-v1-core">Pod [core/v1]</a></LI>
<LI><a href="#poddisruptionbudget-v1-policy">PodDisruptionBudget [policy/v1]</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-v1-scheduling-k8s-io">PriorityClass [scheduling/v1]</a></LI>
<LI><a href="#prioritylevelconfiguration-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfiguration [flowcontrol/v1]</a></LI>
<LI><a href="#replicaset-v1-apps">ReplicaSet [apps/v1]</a></LI>
<LI><a href="#replicationcontroller-v1-core">ReplicationController [core/v1]</a></LI>
<LI><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim [resource/v1beta1]</a></LI>
<LI><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim [resource/v1alpha3]</a></LI>
<LI><a href="#resourceclaimtemplate-v1beta1-resource-k8s-io">ResourceClaimTemplate [resource/v1beta1]</a></LI>
<LI><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate [resource/v1alpha3]</a></LI>
<LI><a href="#resourceclaimtemplatespec-v1beta1-resource-k8s-io">ResourceClaimTemplateSpec [resource/v1beta1]</a></LI>
<LI><a href="#resourceclaimtemplatespec-v1alpha3-resource-k8s-io">ResourceClaimTemplateSpec [resource/v1alpha3]</a></LI>
<LI><a href="#resourcequota-v1-core">ResourceQuota [core/v1]</a></LI>
<LI><a href="#resourceslice-v1beta1-resource-k8s-io">ResourceSlice [resource/v1beta1]</a></LI>
<LI><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice [resource/v1alpha3]</a></LI>
<LI><a href="#role-v1-rbac-authorization-k8s-io">Role [rbac/v1]</a></LI>
<LI><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding [rbac/v1]</a></LI>
<LI><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass [node/v1]</a></LI>
<LI><a href="#scale-v1-autoscaling">Scale [autoscaling/v1]</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="#selfsubjectreview-v1-authentication-k8s-io">SelfSubjectReview [authentication/v1]</a></LI>
<LI><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview [authentication/v1beta1]</a></LI>
<LI><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1]</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="#servicecidr-v1beta1-networking-k8s-io">ServiceCIDR [networking/v1beta1]</a></LI>
<LI><a href="#statefulset-v1-apps">StatefulSet [apps/v1]</a></LI>
<LI><a href="#storageclass-v1-storage-k8s-io">StorageClass [storage/v1]</a></LI>
<LI><a href="#storageversion-v1alpha1-internal-apiserver-k8s-io">StorageVersion [apiserverinternal/v1alpha1]</a></LI>
<LI><a href="#storageversionmigration-v1alpha1-storagemigration-k8s-io">StorageVersionMigration [storagemigration/v1alpha1]</a></LI>
<LI><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview [authorization/v1]</a></LI>
<LI><a href="#tokenrequest-v1-authentication-k8s-io">TokenRequest [authentication/v1]</a></LI>
<LI><a href="#tokenreview-v1-authentication-k8s-io">TokenReview [authentication/v1]</a></LI>
<LI><a href="#validatingadmissionpolicy-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicy [admissionregistration/v1]</a></LI>
<LI><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy [admissionregistration/v1beta1]</a></LI>
<LI><a href="#validatingadmissionpolicybinding-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding [admissionregistration/v1]</a></LI>
<LI><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding [admissionregistration/v1beta1]</a></LI>
<LI><a href="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration [admissionregistration/v1]</a></LI>
<LI><a href="#volumeattachment-v1-storage-k8s-io">VolumeAttachment [storage/v1]</a></LI>
<LI><a href="#volumeattributesclass-v1beta1-storage-k8s-io">VolumeAttributesClass [storage/v1beta1]</a></LI>
<LI><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass [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: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations</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/sig-architecture/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/sig-architecture/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. Finalizers may be processed and removed in any order. Order is NOT enforced because it introduces significant risk of stuck finalizers. finalizers is a shared field, any actor with permission can reorder it. If the finalizer list is processed in order, then this can lead to a situation in which the component responsible for the first finalizer in the list is waiting for a signal (field value, external system, or other) produced by a component responsible for a finalizer later in the list, resulting in a deadlock. Without enforced ordering finalizers are free to order amongst themselves and are not vulnerable to ordering changes in the list.</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 return a 409. Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/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>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: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels</TD></TR>
<TR><TD><CODE>managedFields</CODE><BR /><I><a href="#managedfieldsentry-v1-meta">ManagedFieldsEntry</a> array</I></TD><TD>ManagedFields maps workflow-id and version to the set of fields that are managed by that workflow. This is mostly for internal housekeeping, and users typically shouldn&#39;t need to set or understand this field. A workflow can be the user&#39;s name, a controller&#39;s name, or the name of a specific apply path like &#34;ci-cd&#34;. The set of fields is always in the version that the workflow used when modifying the object.</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: 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 defines the space within which 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: https://kubernetes.io/docs/concepts/overview/working-with-objects/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/sig-architecture/api-conventions.md#concurrency-control-and-consistency</TD></TR>
<TR><TD><CODE>selfLink</CODE><BR /><I>string</I></TD><TD>Deprecated: selfLink is a legacy read-only field that is no longer populated by the system.</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: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="objectmetricsource-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">ObjectMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">MetricSpec [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>describedObject</CODE><BR /><I><a href="#crossversionobjectreference-v2-autoscaling">CrossVersionObjectReference</a></I></TD><TD>describedObject specifies the descriptions of a object,such as kind,name apiVersion</TD></TR>
<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="objectmetricstatus-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">ObjectMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
<TR><TD><CODE>describedObject</CODE><BR /><I><a href="#crossversionobjectreference-v2-autoscaling">CrossVersionObjectReference</a></I></TD><TD>DescribedObject specifies the descriptions of a object,such as kind,name apiVersion</TD></TR>
<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="objectreference-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ObjectReference</span> <span class="v">v1</span> <span class="g">core</span></span></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-v1-batch">CronJobStatus [batch/v1]</a></LI>
<LI><a href="#endpoint-v1-discovery-k8s-io">Endpoint [discovery/v1]</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-v1-events-k8s-io">Event [events/v1]</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/sig-architecture/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/sig-architecture/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>
</DIV>
<DIV class="definition-container" id="opaquedeviceconfiguration-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">OpaqueDeviceConfiguration</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>OpaqueDeviceConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<P>OpaqueDeviceConfiguration contains configuration parameters for a driver in a format defined by the driver vendor.</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="#opaquedeviceconfiguration-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceallocationconfiguration-v1beta1-resource-k8s-io">DeviceAllocationConfiguration [resource/v1beta1]</a></LI>
<LI><a href="#deviceclaimconfiguration-v1beta1-resource-k8s-io">DeviceClaimConfiguration [resource/v1beta1]</a></LI>
<LI><a href="#deviceclassconfiguration-v1beta1-resource-k8s-io">DeviceClassConfiguration [resource/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 used to determine which kubelet plugin needs to be passed these configuration parameters. An admission policy provided by the driver developer could use this to decide whether it needs to validate them. Must be a DNS subdomain and should end with a DNS domain owned by the vendor of the driver.</TD></TR>
<TR><TD><CODE>parameters</CODE></TD><TD>Parameters can contain arbitrary data. It is the responsibility of the driver developer to handle validation and versioning. Typically this includes self-identification and a version (&#34;kind&#34; + &#34;apiVersion&#34; for Kubernetes types), with conversion between different versions. The length of the raw data must be smaller or equal to 10 Ki.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="overhead-v1-node-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">Overhead</span> <span class="v">v1</span> <span class="g">node.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Overhead</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Overhead structure represents the resource overhead associated with running a pod.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass [node/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>podFixed</CODE><BR /><I>object</I></TD><TD>podFixed represents the fixed resource overhead associated with running a pod.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="ownerreference-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">OwnerReference</span> <span class="v">v1</span> <span class="g">meta</span></span></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. An owning object must be in the same namespace as the dependent, or be cluster-scoped, 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. See https://kubernetes.io/docs/concepts/architecture/garbage-collection/#foreground-deletion for how the garbage collector interacts with this field and enforces the foreground deletion. 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/sig-architecture/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>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>
</DIV>
<DIV class="definition-container" id="paramkind-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ParamKind</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>ParamKind</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ParamKind is a tuple of Group Kind and Version.</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="#paramkind-v1beta1-admissionregistration-k8s-io">v1beta1</a>
<a href="#paramkind-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="#validatingadmissionpolicyspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/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 is the API group version the resources belong to. In format of &#34;group/version&#34;. Required.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the API kind the resources belong to. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="paramref-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ParamRef</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>ParamRef</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ParamRef describes how to locate the params to be used as input to expressions of rules applied by a policy binding.</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="#paramref-v1beta1-admissionregistration-k8s-io">v1beta1</a>
<a href="#paramref-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="#validatingadmissionpolicybindingspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec [admissionregistration/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 resource being referenced. One of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset. A single parameter used for all admission requests can be configured by setting the `name` field, leaving `selector` blank, and setting namespace if `paramKind` is namespace-scoped.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>namespace is the namespace of the referenced resource. Allows limiting the search for params to a specific namespace. Applies to both `name` and `selector` fields. A per-namespace parameter may be used by specifying a namespace-scoped `paramKind` in the policy and leaving this field empty. - If `paramKind` is cluster-scoped, this field MUST be unset. Setting this field results in a configuration error. - If `paramKind` is namespace-scoped, the namespace of the object being evaluated for admission will be used when this field is left unset. Take care that if this is left empty the binding must not match any cluster-scoped resources, which will result in an error.</TD></TR>
<TR><TD><CODE>parameterNotFoundAction</CODE><BR /><I>string</I></TD><TD>`parameterNotFoundAction` controls the behavior of the binding when the resource exists, and name or selector is valid, but there are no parameters matched by the binding. If the value is set to `Allow`, then no matched parameters will be treated as successful validation by the binding. If set to `Deny`, then no matched parameters will be subject to the `failurePolicy` of the policy. Allowed values are `Allow` or `Deny` Required</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector can be used to match multiple param objects based on their labels. Supply selector: {} to match all resources of the ParamKind. If multiple params are found, they are all evaluated with the policy expressions and the results are ANDed together. One of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="parentreference-v1beta1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ParentReference</span> <span class="v">v1beta1</span> <span class="g">networking.k8s.io</span></span></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>v1beta1</CODE></TD><TD><CODE>ParentReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ParentReference describes a reference to a parent object.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ipaddressspec-v1beta1-networking-k8s-io">IPAddressSpec [networking/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 group of the object being referenced.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the object being referenced.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of the object being referenced.</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>Resource is the resource of the object being referenced.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="patch-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">Patch</span> <span class="v">v1</span> <span class="g">meta</span></span></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>
</DIV>
<DIV class="definition-container" id="persistentvolumeclaimcondition-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PersistentVolumeClaimCondition</span> <span class="v">v1</span> <span class="g">core</span></span></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 contains 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>lastProbeTime is the time we probed the condition.</TD></TR>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastTransitionTime is the time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is the human-readable message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason is a unique, this should be a short, machine understandable string that gives the reason for condition&#39;s last transition. If it reports &#34;Resizing&#34; that means the underlying persistent volume is being resized.</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/reference/kubernetes-api/config-and-storage-resources/persistent-volume-claim-v1/#:~:text=state%20of%20pvc-,conditions.status,-(string)%2C%20required</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/reference/kubernetes-api/config-and-storage-resources/persistent-volume-claim-v1/#:~:text=set%20to%20%27ResizeStarted%27.-,PersistentVolumeClaimCondition,-contains%20details%20about</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="persistentvolumeclaimtemplate-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PersistentVolumeClaimTemplate</span> <span class="v">v1</span> <span class="g">core</span></span></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>PersistentVolumeClaimTemplate</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PersistentVolumeClaimTemplate is used to produce PersistentVolumeClaim objects as part of an EphemeralVolumeSource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ephemeralvolumesource-v1-core">EphemeralVolumeSource [core/v1]</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>May contain labels and annotations that will be copied into the PVC when creating it. No other fields are allowed and will be rejected during validation.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec</a></I></TD><TD>The specification for the PersistentVolumeClaim. The entire content is copied unchanged into the PVC that gets created from this template. The same fields as in a PersistentVolumeClaim are also valid here.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="persistentvolumeclaimvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PersistentVolumeClaimVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>readOnly Will force the ReadOnly setting in VolumeMounts. Default false.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="photonpersistentdiskvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PhotonPersistentDiskVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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>pdID is the ID that identifies Photon Controller persistent disk</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podaffinity-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodAffinity</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="podaffinityterm-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodAffinityTerm</span> <span class="v">v1</span> <span class="g">core</span></span></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. If it&#39;s null, this PodAffinityTerm matches with no Pods.</TD></TR>
<TR><TD><CODE>matchLabelKeys</CODE><BR /><I>string array</I></TD><TD>MatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with `labelSelector` as `key in (value)` to select the group of existing pods which pods will be taken into consideration for the incoming pod&#39;s pod (anti) affinity. Keys that don&#39;t exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both matchLabelKeys and labelSelector. Also, matchLabelKeys cannot be set when labelSelector isn&#39;t set. This is a beta field and requires enabling MatchLabelKeysInPodAffinity feature gate (enabled by default).</TD></TR>
<TR><TD><CODE>mismatchLabelKeys</CODE><BR /><I>string array</I></TD><TD>MismatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with `labelSelector` as `key notin (value)` to select the group of existing pods which pods will be taken into consideration for the incoming pod&#39;s pod (anti) affinity. Keys that don&#39;t exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both mismatchLabelKeys and labelSelector. Also, mismatchLabelKeys cannot be set when labelSelector isn&#39;t set. This is a beta field and requires enabling MatchLabelKeysInPodAffinity feature gate (enabled by default).</TD></TR>
<TR><TD><CODE>namespaceSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over the set of namespaces that the term applies to. The term is applied to the union of the namespaces selected by this field and the ones listed in the namespaces field. null selector and null or empty namespaces list means &#34;this pod&#39;s namespace&#34;. An empty selector ({}) matches all namespaces.</TD></TR>
<TR><TD><CODE>namespaces</CODE><BR /><I>string array</I></TD><TD>namespaces specifies a static list of namespace names that the term applies to. The term is applied to the union of the namespaces listed in this field and the ones selected by namespaceSelector. null or empty namespaces list and null namespaceSelector 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>
</DIV>
<DIV class="definition-container" id="podantiaffinity-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodAntiAffinity</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="podcondition-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodCondition</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="poddnsconfig-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodDNSConfig</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="poddnsconfigoption-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodDNSConfigOption</span> <span class="v">v1</span> <span class="g">core</span></span></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>Name is this DNS resolver option&#39;s name. Required.</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>Value is this DNS resolver option&#39;s value.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podfailurepolicy-v1-batch">
<H2 class="definition"><span class="gvk"><span class="k">PodFailurePolicy</span> <span class="v">v1</span> <span class="g">batch</span></span></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>PodFailurePolicy</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodFailurePolicy describes how failed pods influence the backoffLimit.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#jobspec-v1-batch">JobSpec [batch/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#podfailurepolicyrule-v1-batch">PodFailurePolicyRule</a> array</I></TD><TD>A list of pod failure policy rules. The rules are evaluated in order. Once a rule matches a Pod failure, the remaining of the rules are ignored. When no rule matches the Pod failure, the default handling applies - the counter of pod failures is incremented and it is checked against the backoffLimit. At most 20 elements are allowed.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podfailurepolicyonexitcodesrequirement-v1-batch">
<H2 class="definition"><span class="gvk"><span class="k">PodFailurePolicyOnExitCodesRequirement</span> <span class="v">v1</span> <span class="g">batch</span></span></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>PodFailurePolicyOnExitCodesRequirement</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodFailurePolicyOnExitCodesRequirement describes the requirement for handling a failed pod based on its container exit codes. In particular, it lookups the .state.terminated.exitCode for each app container and init container status, represented by the .status.containerStatuses and .status.initContainerStatuses fields in the Pod status, respectively. Containers completed with success (exit code 0) are excluded from the requirement check.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podfailurepolicyrule-v1-batch">PodFailurePolicyRule [batch/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>Restricts the check for exit codes to the container with the specified name. When null, the rule applies to all containers. When specified, it should match one the container or initContainer names in the pod template.</TD></TR>
<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>Represents the relationship between the container exit code(s) and the specified values. Containers completed with success (exit code 0) are excluded from the requirement check. Possible values are: - In: the requirement is satisfied if at least one container exit code (might be multiple if there are multiple containers not restricted by the &#39;containerName&#39; field) is in the set of specified values. - NotIn: the requirement is satisfied if at least one container exit code (might be multiple if there are multiple containers not restricted by the &#39;containerName&#39; field) is not in the set of specified values. Additional values are considered to be added in the future. Clients should react to an unknown operator by assuming the requirement is not satisfied.</TD></TR>
<TR><TD><CODE>values</CODE><BR /><I>integer array</I></TD><TD>Specifies the set of values. Each returned container exit code (might be multiple in case of multiple containers) is checked against this set of values with respect to the operator. The list of values must be ordered and must not contain duplicates. Value &#39;0&#39; cannot be used for the In operator. At least one element is required. At most 255 elements are allowed.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podfailurepolicyonpodconditionspattern-v1-batch">
<H2 class="definition"><span class="gvk"><span class="k">PodFailurePolicyOnPodConditionsPattern</span> <span class="v">v1</span> <span class="g">batch</span></span></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>PodFailurePolicyOnPodConditionsPattern</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodFailurePolicyOnPodConditionsPattern describes a pattern for matching an actual pod condition type.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podfailurepolicyrule-v1-batch">PodFailurePolicyRule [batch/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Specifies the required Pod condition status. To match a pod condition it is required that the specified status equals the pod condition status. Defaults to True.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Specifies the required Pod condition type. To match a pod condition it is required that specified type equals the pod condition type.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podfailurepolicyrule-v1-batch">
<H2 class="definition"><span class="gvk"><span class="k">PodFailurePolicyRule</span> <span class="v">v1</span> <span class="g">batch</span></span></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>PodFailurePolicyRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of onExitCodes and onPodConditions, but not both, can be used in each rule.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podfailurepolicy-v1-batch">PodFailurePolicy [batch/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>Specifies the action taken on a pod failure when the requirements are satisfied. Possible values are: - FailJob: indicates that the pod&#39;s job is marked as Failed and all running pods are terminated. - FailIndex: indicates that the pod&#39;s index is marked as Failed and will not be restarted. This value is beta-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (enabled by default). - Ignore: indicates that the counter towards the .backoffLimit is not incremented and a replacement pod is created. - Count: indicates that the pod is handled in the default way - the counter towards the .backoffLimit is incremented. Additional values are considered to be added in the future. Clients should react to an unknown action by skipping the rule.</TD></TR>
<TR><TD><CODE>onExitCodes</CODE><BR /><I><a href="#podfailurepolicyonexitcodesrequirement-v1-batch">PodFailurePolicyOnExitCodesRequirement</a></I></TD><TD>Represents the requirement on the container exit codes.</TD></TR>
<TR><TD><CODE>onPodConditions</CODE><BR /><I><a href="#podfailurepolicyonpodconditionspattern-v1-batch">PodFailurePolicyOnPodConditionsPattern</a> array</I></TD><TD>Represents the requirement on the pod conditions. The requirement is represented as a list of pod condition patterns. The requirement is satisfied if at least one pattern matches an actual pod condition. At most 20 elements are allowed.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podip-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodIP</span> <span class="v">v1</span> <span class="g">core</span></span></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>PodIP</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodIP represents a single IP address allocated 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="#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>ip</CODE><BR /><I>string</I></TD><TD>IP is the IP address assigned to the pod</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podos-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodOS</span> <span class="v">v1</span> <span class="g">core</span></span></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>PodOS</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodOS defines the OS parameters 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="#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>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the operating system. The currently supported values are linux and windows. Additional value may be defined in future and can be one of: https://github.com/opencontainers/runtime-spec/blob/master/config.md#platform-specific-configuration Clients should expect to handle additional values and treat unrecognized values in this field as os: null</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podreadinessgate-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodReadinessGate</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="podresourceclaim-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodResourceClaim</span> <span class="v">v1</span> <span class="g">core</span></span></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>PodResourceClaim</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodResourceClaim references exactly one ResourceClaim, either directly or by naming a ResourceClaimTemplate which is then turned into a ResourceClaim for the pod.
It adds a name to it that uniquely identifies the ResourceClaim inside the Pod. Containers that need access to the ResourceClaim reference it with this name.</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>name</CODE><BR /><I>string</I></TD><TD>Name uniquely identifies this resource claim inside the pod. This must be a DNS_LABEL.</TD></TR>
<TR><TD><CODE>resourceClaimName</CODE><BR /><I>string</I></TD><TD>ResourceClaimName is the name of a ResourceClaim object in the same namespace as this pod. Exactly one of ResourceClaimName and ResourceClaimTemplateName must be set.</TD></TR>
<TR><TD><CODE>resourceClaimTemplateName</CODE><BR /><I>string</I></TD><TD>ResourceClaimTemplateName is the name of a ResourceClaimTemplate object in the same namespace as this pod. The template will be used to create a new ResourceClaim, which will be bound to this pod. When this pod is deleted, the ResourceClaim will also be deleted. The pod name and resource name, along with a generated component, will be used to form a unique name for the ResourceClaim, which will be recorded in pod.status.resourceClaimStatuses. This field is immutable and no changes will be made to the corresponding ResourceClaim by the control plane after creating the ResourceClaim. Exactly one of ResourceClaimName and ResourceClaimTemplateName must be set.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podschedulinggate-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodSchedulingGate</span> <span class="v">v1</span> <span class="g">core</span></span></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>PodSchedulingGate</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodSchedulingGate is associated to a Pod to guard its scheduling.</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>name</CODE><BR /><I>string</I></TD><TD>Name of the scheduling gate. Each scheduling gate must have a unique name field.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podsecuritycontext-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PodSecurityContext</span> <span class="v">v1</span> <span class="g">core</span></span></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>appArmorProfile</CODE><BR /><I><a href="#apparmorprofile-v1-core">AppArmorProfile</a></I></TD><TD>appArmorProfile is the AppArmor options to use by the containers in this pod. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<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. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<TR><TD><CODE>fsGroupChangePolicy</CODE><BR /><I>string</I></TD><TD>fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod. This field will only apply to volume types which support fsGroup based ownership(and permissions). It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are &#34;OnRootMismatch&#34; and &#34;Always&#34;. If not specified, &#34;Always&#34; is used. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<TR><TD><CODE>seLinuxChangePolicy</CODE><BR /><I>string</I></TD><TD>seLinuxChangePolicy defines how the container&#39;s SELinux label is applied to all volumes used by the Pod. It has no effect on nodes that do not support SELinux or to volumes does not support SELinux. Valid values are &#34;MountOption&#34; and &#34;Recursive&#34;. &#34;Recursive&#34; means relabeling of all files on all Pod volumes by the container runtime. This may be slow for large volumes, but allows mixing privileged and unprivileged Pods sharing the same volume on the same node. &#34;MountOption&#34; mounts all eligible Pod volumes with `-o context` mount option. This requires all Pods that share the same volume to use the same SELinux label. It is not possible to share the same volume among privileged and unprivileged Pods. Eligible volumes are in-tree FibreChannel and iSCSI volumes, and all CSI volumes whose CSI driver announces SELinux support by setting spec.seLinuxMount: true in their CSIDriver instance. Other volumes are always re-labelled recursively. &#34;MountOption&#34; value is allowed only when SELinuxMount feature gate is enabled. If not specified and SELinuxMount feature gate is enabled, &#34;MountOption&#34; is used. If not specified and SELinuxMount feature gate is disabled, &#34;MountOption&#34; is used for ReadWriteOncePod volumes and &#34;Recursive&#34; for all other volumes. This field affects only Pods that have SELinux label set, either in PodSecurityContext or in SecurityContext of all containers. All Pods that use the same volume should use the same seLinuxChangePolicy, otherwise some pods can get stuck in ContainerCreating state. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<TR><TD><CODE>seccompProfile</CODE><BR /><I><a href="#seccompprofile-v1-core">SeccompProfile</a></I></TD><TD>The seccomp options to use by the containers in this pod. Note that this field cannot be set when spec.os.name is windows.</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 and fsGroup (if specified). If the SupplementalGroupsPolicy feature is enabled, the supplementalGroupsPolicy field determines whether these are in addition to or instead of any group memberships defined in the container image. If unspecified, no additional groups are added, though group memberships defined in the container image may still be used, depending on the supplementalGroupsPolicy field. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<TR><TD><CODE>supplementalGroupsPolicy</CODE><BR /><I>string</I></TD><TD>Defines how supplemental groups of the first container processes are calculated. Valid values are &#34;Merge&#34; and &#34;Strict&#34;. If not specified, &#34;Merge&#34; is used. (Alpha) Using the field requires the SupplementalGroupsPolicy feature gate to be enabled and the container runtime must implement support for this feature. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<TR><TD><CODE>windowsOptions</CODE><BR /><I><a href="#windowssecuritycontextoptions-v1-core">WindowsSecurityContextOptions</a></I></TD><TD>The Windows specific settings applied to all containers. If unspecified, the options within a container&#39;s SecurityContext will be used. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is linux.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podsmetricsource-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">PodsMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">MetricSpec [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
<TR><TD><CODE>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="podsmetricstatus-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">PodsMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</TD></TR>
<TR><TD><CODE>metric</CODE><BR /><I><a href="#metricidentifier-v2-autoscaling">MetricIdentifier</a></I></TD><TD>metric identifies the target metric by name and selector</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="policyrule-v1-rbac-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">PolicyRule</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></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-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. &#34;&#34; represents the core API group and &#34;*&#34; represents all API groups.</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.</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 contained in this rule. &#39;\*&#39; represents all verbs.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="policyruleswithsubjects-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">PolicyRulesWithSubjects</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PolicyRulesWithSubjects</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PolicyRulesWithSubjects prescribes a test that applies to a request to an apiserver. The test considers the subject making the request, the verb being requested, and the resource to be acted upon. This PolicyRulesWithSubjects matches a request if and only if both (a) at least one member of subjects matches the request and (b) at least one member of resourceRules or nonResourceRules matches the request.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#flowschemaspec-v1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>nonResourceRules</CODE><BR /><I><a href="#nonresourcepolicyrule-v1-flowcontrol-apiserver-k8s-io">NonResourcePolicyRule</a> array</I></TD><TD>`nonResourceRules` is a list of NonResourcePolicyRules that identify matching requests according to their verb and the target non-resource URL.</TD></TR>
<TR><TD><CODE>resourceRules</CODE><BR /><I><a href="#resourcepolicyrule-v1-flowcontrol-apiserver-k8s-io">ResourcePolicyRule</a> array</I></TD><TD>`resourceRules` is a slice of ResourcePolicyRules that identify matching requests according to their verb and the target resource. At least one of `resourceRules` and `nonResourceRules` has to be non-empty.</TD></TR>
<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1-flowcontrol-apiserver-k8s-io">Subject</a> array</I></TD><TD>subjects is the list of normal user, serviceaccount, or group that this rule cares about. There must be at least one member in this slice. A slice that includes both the system:authenticated and system:unauthenticated user groups matches every request. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="portstatus-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PortStatus</span> <span class="v">v1</span> <span class="g">core</span></span></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>PortStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PortStatus represents the error condition of a service port</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#loadbalanceringress-v1-core">LoadBalancerIngress [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>Error is to record the problem with the service port The format of the error shall comply with the following rules: - built-in error values shall be specified in this file and those shall use CamelCase names - cloud provider specific error values must have names that comply with the format foo.example.com/CamelCase.</TD></TR>
<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>Port is the port number of the service port of which status is recorded here</TD></TR>
<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>Protocol is the protocol of the service port of which status is recorded here The supported values are: &#34;TCP&#34;, &#34;UDP&#34;, &#34;SCTP&#34;</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="portworxvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PortworxVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>readOnly 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>
</DIV>
<DIV class="definition-container" id="preconditions-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">Preconditions</span> <span class="v">v1</span> <span class="g">meta</span></span></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>resourceVersion</CODE><BR /><I>string</I></TD><TD>Specifies the target ResourceVersion</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>Specifies the target UID.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="preferredschedulingterm-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">PreferredSchedulingTerm</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="prioritylevelconfigurationcondition-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">PriorityLevelConfigurationCondition</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PriorityLevelConfigurationCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PriorityLevelConfigurationCondition defines the condition of priority level.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#prioritylevelconfigurationstatus-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationStatus [flowcontrol/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>`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 message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>`reason` is a 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. Required.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>`type` is the type of the condition. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="prioritylevelconfigurationreference-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">PriorityLevelConfigurationReference</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PriorityLevelConfigurationReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PriorityLevelConfigurationReference contains information that points to the &#34;request-priority&#34; being used.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#flowschemaspec-v1-flowcontrol-apiserver-k8s-io">FlowSchemaSpec [flowcontrol/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 priority level configuration being referenced Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="probe-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">Probe</span> <span class="v">v1</span> <span class="g">core</span></span></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>
<LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [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>Exec specifies a command to execute in the container.</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>grpc</CODE><BR /><I><a href="#grpcaction-v1-core">GRPCAction</a></I></TD><TD>GRPC specifies a GRPC HealthCheckRequest.</TD></TR>
<TR><TD><CODE>httpGet</CODE><BR /><I><a href="#httpgetaction-v1-core">HTTPGetAction</a></I></TD><TD>HTTPGet specifies an HTTP GET 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 and startup. 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 a connection to a TCP port.</TD></TR>
<TR><TD><CODE>terminationGracePeriodSeconds</CODE><BR /><I>integer</I></TD><TD>Optional duration in seconds the pod needs to terminate gracefully upon probe failure. 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. If this value is nil, the pod&#39;s terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is a beta field and requires enabling ProbeTerminationGracePeriod feature gate. Minimum value is 1. spec.terminationGracePeriodSeconds is used if unset.</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>
</DIV>
<DIV class="definition-container" id="projectedvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ProjectedVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>defaultMode are the mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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>sources is the list of volume projections. Each entry in this list handles one source.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="quantity-resource-core">
<H2 class="definition"><span class="gvk"><span class="k">Quantity</span> <span class="v">resource</span> <span class="g">core</span></span></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 AsInt64() 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:
- No precision is lost - No fractional digits will be emitted - 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 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="#basicdevice-v1alpha3-resource-k8s-io">BasicDevice [resource/v1alpha3]</a></LI>
<LI><a href="#csistoragecapacity-v1-storage-k8s-io">CSIStorageCapacity [storage/v1]</a></LI>
<LI><a href="#containerstatus-v1-core">ContainerStatus [core/v1]</a></LI>
<LI><a href="#devicecapacity-v1beta1-resource-k8s-io">DeviceCapacity [resource/v1beta1]</a></LI>
<LI><a href="#emptydirvolumesource-v1-core">EmptyDirVolumeSource [core/v1]</a></LI>
<LI><a href="#limitrangeitem-v1-core">LimitRangeItem [core/v1]</a></LI>
<LI><a href="#metrictarget-v2-autoscaling">MetricTarget [autoscaling/v2]</a></LI>
<LI><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus [autoscaling/v2]</a></LI>
<LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
<LI><a href="#overhead-v1-node-k8s-io">Overhead [node/v1]</a></LI>
<LI><a href="#persistentvolumeclaimstatus-v1-core">PersistentVolumeClaimStatus [core/v1]</a></LI>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
<LI><a href="#resourcefieldselector-v1-core">ResourceFieldSelector [core/v1]</a></LI>
<LI><a href="#resourcequotaspec-v1-core">ResourceQuotaSpec [core/v1]</a></LI>
<LI><a href="#resourcequotastatus-v1-core">ResourceQuotaStatus [core/v1]</a></LI>
<LI><a href="#resourcerequirements-v1-core">ResourceRequirements [core/v1]</a></LI>
<LI><a href="#volumeresourcerequirements-v1-core">VolumeResourceRequirements [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="queuingconfiguration-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">QueuingConfiguration</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>QueuingConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<P>QueuingConfiguration holds the configuration parameters for queuing</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#limitresponse-v1-flowcontrol-apiserver-k8s-io">LimitResponse [flowcontrol/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>handSize</CODE><BR /><I>integer</I></TD><TD>`handSize` is a small positive number that configures the shuffle sharding of requests into queues. When enqueuing a request at this priority level the request&#39;s flow identifier (a string pair) is hashed and the hash value is used to shuffle the list of queues and deal a hand of the size specified here. The request is put into one of the shortest queues in that hand. `handSize` must be no larger than `queues`, and should be significantly smaller (so that a few heavy flows do not saturate most of the queues). See the user-facing documentation for more extensive guidance on setting this field. This field has a default value of 8.</TD></TR>
<TR><TD><CODE>queueLengthLimit</CODE><BR /><I>integer</I></TD><TD>`queueLengthLimit` is the maximum number of requests allowed to be waiting in a given queue of this priority level at a time; excess requests are rejected. This value must be positive. If not specified, it will be defaulted to 50.</TD></TR>
<TR><TD><CODE>queues</CODE><BR /><I>integer</I></TD><TD>`queues` is the number of queues for this priority level. The queues exist independently at each apiserver. The value must be positive. Setting it to 1 effectively precludes shufflesharding and thus makes the distinguisher method of associated flow schemas irrelevant. This field has a default value of 64.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="quobytevolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">QuobyteVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>tenant</CODE><BR /><I>string</I></TD><TD>tenant owning the given Quobyte volume in the Backend Used with dynamically provisioned Quobyte volumes, value is set by the plugin</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>
</DIV>
<DIV class="definition-container" id="rbdpersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">RBDPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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>image is the rados image name. More info: https://examples.k8s.io/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://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>monitors is a collection of Ceph monitors. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>pool is the rados pool name. Default is rbd. More info: https://examples.k8s.io/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://examples.k8s.io/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://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>user is the rados user name. Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="rbdvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">RBDVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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>image is the rados image name. More info: https://examples.k8s.io/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://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>monitors is a collection of Ceph monitors. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>pool is the rados pool name. Default is rbd. More info: https://examples.k8s.io/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://examples.k8s.io/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://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>user is the rados user name. Default is admin. More info: https://examples.k8s.io/volumes/rbd/README.md#how-to-use-it</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="replicasetcondition-v1-apps">
<H2 class="definition"><span class="gvk"><span class="k">ReplicaSetCondition</span> <span class="v">v1</span> <span class="g">apps</span></span></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-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>
</DIV>
<DIV class="definition-container" id="replicationcontrollercondition-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ReplicationControllerCondition</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="resourceattributes-v1-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ResourceAttributes</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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-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>fieldSelector</CODE><BR /><I><a href="#fieldselectorattributes-v1-authorization-k8s-io">FieldSelectorAttributes</a></I></TD><TD>fieldSelector describes the limitation on access based on field. It can only limit access, not broaden it. This field is alpha-level. To use this field, you must enable the `AuthorizeWithSelectors` feature gate (disabled by default).</TD></TR>
<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>labelSelector</CODE><BR /><I><a href="#labelselectorattributes-v1-authorization-k8s-io">LabelSelectorAttributes</a></I></TD><TD>labelSelector describes the limitation on access based on labels. It can only limit access, not broaden it. This field is alpha-level. To use this field, you must enable the `AuthorizeWithSelectors` feature gate (disabled by default).</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>
</DIV>
<DIV class="definition-container" id="resourceclaim-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ResourceClaim</span> <span class="v">v1</span> <span class="g">core</span></span></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>ResourceClaim</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceClaim references one entry in PodSpec.ResourceClaims.</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="#resourceclaim-v1beta1-resource-k8s-io">v1beta1</a>
<a href="#resourceclaim-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourcerequirements-v1-core">ResourceRequirements [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 must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container.</TD></TR>
<TR><TD><CODE>request</CODE><BR /><I>string</I></TD><TD>Request is the name chosen for a request in the referenced claim. If empty, everything from the claim is made available, otherwise only the result of this request.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="resourceclaimconsumerreference-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ResourceClaimConsumerReference</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ResourceClaimConsumerReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceClaimConsumerReference contains enough information to let you locate the consumer of a ResourceClaim. The user must be a resource in the same namespace as the ResourceClaim.</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="#resourceclaimconsumerreference-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaimstatus-v1beta1-resource-k8s-io">ResourceClaimStatus [resource/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. It is empty for the core API. This matches the group in the APIVersion that is used when creating the resources.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of resource being referenced.</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>Resource is the type of resource being referenced, for example &#34;pods&#34;.</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID identifies exactly one incarnation of the resource.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="resourcefieldselector-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ResourceFieldSelector</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="resourcehealth-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ResourceHealth</span> <span class="v">v1</span> <span class="g">core</span></span></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>ResourceHealth</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceHealth represents the health of a resource. It has the latest device health information. This is a part of KEP https://kep.k8s.io/4680.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourcestatus-v1-core">ResourceStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>health</CODE><BR /><I>string</I></TD><TD>Health of the resource. can be one of: - Healthy: operates as normal - Unhealthy: reported unhealthy. We consider this a temporary health issue since we do not have a mechanism today to distinguish temporary and permanent issues. - Unknown: The status cannot be determined. For example, Device Plugin got unregistered and hasn&#39;t been re-registered since. In future we may want to introduce the PermanentlyUnhealthy Status.</TD></TR>
<TR><TD><CODE>resourceID</CODE><BR /><I>string</I></TD><TD>ResourceID is the unique identifier of the resource. See the ResourceID type for more information.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="resourcemetricsource-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">ResourceMetricSource</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">MetricSpec [autoscaling/v2]</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>target</CODE><BR /><I><a href="#metrictarget-v2-autoscaling">MetricTarget</a></I></TD><TD>target specifies the target value for the given metric</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="resourcemetricstatus-v2-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">ResourceMetricStatus</span> <span class="v">v2</span> <span class="g">autoscaling</span></span></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>v2</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-v2-autoscaling">MetricStatus [autoscaling/v2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>current</CODE><BR /><I><a href="#metricvaluestatus-v2-autoscaling">MetricValueStatus</a></I></TD><TD>current contains the current value for the given metric</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>
</DIV>
<DIV class="definition-container" id="resourcepolicyrule-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ResourcePolicyRule</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourcePolicyRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourcePolicyRule is a predicate that matches some resource requests, testing the request&#39;s verb and the target resource. A ResourcePolicyRule matches a resource request if and only if: (a) at least one member of verbs matches the request, (b) at least one member of apiGroups matches the request, (c) at least one member of resources matches the request, and (d) either (d1) the request does not specify a namespace (i.e., `Namespace==&#34;&#34;`) and clusterScope is true or (d2) the request specifies a namespace and least one member of namespaces matches the request&#39;s namespace.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#policyruleswithsubjects-v1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/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 a list of matching API groups and may not be empty. &#34;*&#34; matches all API groups and, if present, must be the only entry. Required.</TD></TR>
<TR><TD><CODE>clusterScope</CODE><BR /><I>boolean</I></TD><TD>`clusterScope` indicates whether to match requests that do not specify a namespace (which happens either because the resource is not namespaced or the request targets all namespaces). If this field is omitted or false then the `namespaces` field must contain a non-empty list.</TD></TR>
<TR><TD><CODE>namespaces</CODE><BR /><I>string array</I></TD><TD>`namespaces` is a list of target namespaces that restricts matches. A request that specifies a target namespace matches only if either (a) this list contains that target namespace or (b) this list contains &#34;*&#34;. Note that &#34;*&#34; matches any specified namespace but does not match a request that _does not specify_ a namespace (see the `clusterScope` field for that). This list may be empty, but only if `clusterScope` is true.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>`resources` is a list of matching resources (i.e., lowercase and plural) with, if desired, subresource. For example, [ &#34;services&#34;, &#34;nodes/status&#34; ]. This list may not be empty. &#34;*&#34; matches all resources and, if present, must be the only entry. Required.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>`verbs` is a list of matching verbs and may not be empty. &#34;*&#34; matches all verbs and, if present, must be the only entry. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="resourcepool-v1beta1-resource-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ResourcePool</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ResourcePool</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourcePool describes the pool that ResourceSlices belong 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="#resourcepool-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceslicespec-v1beta1-resource-k8s-io">ResourceSliceSpec [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>generation</CODE><BR /><I>integer</I></TD><TD>Generation tracks the change in a pool over time. Whenever a driver changes something about one or more of the resources in a pool, it must change the generation in all ResourceSlices which are part of that pool. Consumers of ResourceSlices should only consider resources from the pool with the highest generation number. The generation may be reset by drivers, which should be fine for consumers, assuming that all ResourceSlices in a pool are updated to match or deleted. Combined with ResourceSliceCount, this mechanism enables consumers to detect pools which are comprised of multiple ResourceSlices and are in an incomplete state.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is used to identify the pool. For node-local devices, this is often the node name, but this is not required. It must not be longer than 253 characters and must consist of one or more DNS sub-domains separated by slashes. This field is immutable.</TD></TR>
<TR><TD><CODE>resourceSliceCount</CODE><BR /><I>integer</I></TD><TD>ResourceSliceCount is the total number of ResourceSlices in the pool at this generation number. Must be greater than zero. Consumers can use this to check whether they have seen all ResourceSlices belonging to the same pool.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="resourcerequirements-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ResourceRequirements</span> <span class="v">v1</span> <span class="g">core</span></span></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="#containerstatus-v1-core">ContainerStatus [core/v1]</a></LI>
<LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</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>claims</CODE><BR /><I><a href="#resourceclaim-v1-core">ResourceClaim</a> array</I></TD><TD>Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container. This is an alpha field and requires enabling the DynamicResourceAllocation feature gate. This field is immutable. It can only be set for containers.</TD></TR>
<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-resources-containers/</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. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="resourcerule-v1-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ResourceRule</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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-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>
</DIV>
<DIV class="definition-container" id="resourcestatus-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ResourceStatus</span> <span class="v">v1</span> <span class="g">core</span></span></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>ResourceStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceStatus represents the status of a single resource allocated to a Pod.</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>name</CODE><BR /><I>string</I></TD><TD>Name of the resource. Must be unique within the pod and in case of non-DRA resource, match one of the resources from the pod spec. For DRA resources, the value must be &#34;claim:&lt;claim_name&gt;/&lt;request&gt;&#34;. When this status is reported about a container, the &#34;claim_name&#34; and &#34;request&#34; must match one of the claims of this container.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcehealth-v1-core">ResourceHealth</a> array</I></TD><TD>List of unique resources health. Each element in the list contains an unique resource ID and its health. At a minimum, for the lifetime of a Pod, resource ID must uniquely identify the resource allocated to the Pod on the Node. If other Pod on the same Node reports the status with the same resource ID, it must be the same resource they share. See ResourceID type definition for a specific format it has in various use cases.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="roleref-v1-rbac-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">RoleRef</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></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-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>
</DIV>
<DIV class="definition-container" id="rollingupdatestatefulsetstrategy-v1-apps">
<H2 class="definition"><span class="gvk"><span class="k">RollingUpdateStatefulSetStrategy</span> <span class="v">v1</span> <span class="g">apps</span></span></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-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>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 up. This can not be 0. Defaults to 1. This field is alpha-level and is only honored by servers that enable the MaxUnavailableStatefulSet feature. The field applies to all pods in the range 0 to Replicas-1. That means if there is any unavailable pod in the range 0 to Replicas-1, it will be counted towards MaxUnavailable.</TD></TR>
<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>Partition indicates the ordinal at which the StatefulSet should be partitioned for updates. During a rolling update, all pods from ordinal Replicas-1 to Partition are updated. All pods from ordinal Partition-1 to 0 remain untouched. This is helpful in being able to do a canary based deployment. The default value is 0.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="rulewithoperations-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">RuleWithOperations</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</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="#mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook [admissionregistration/v1]</a></LI>
<LI><a href="#validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook [admissionregistration/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 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, DELETE, CONNECT or * for all of those operations and any future admission operations that are added. 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>
<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>scope specifies the scope of this rule. Valid values are &#34;Cluster&#34;, &#34;Namespaced&#34;, and &#34;*&#34; &#34;Cluster&#34; means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. &#34;Namespaced&#34; means that only namespaced resources will match this rule. &#34;*&#34; means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is &#34;*&#34;.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="selinuxoptions-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SELinuxOptions</span> <span class="v">v1</span> <span class="g">core</span></span></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="#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>
</DIV>
<DIV class="definition-container" id="scale-v1-autoscaling">
<H2 class="definition"><span class="gvk"><span class="k">Scale</span> <span class="v">v1</span> <span class="g">autoscaling</span></span></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>
<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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#scalespec-v1-autoscaling">ScaleSpec</a></I></TD><TD>spec defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/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>status is the current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="scaleiopersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ScaleIOPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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;. Default is &#34;xfs&#34;</TD></TR>
<TR><TD><CODE>gateway</CODE><BR /><I>string</I></TD><TD>gateway is the host address of the ScaleIO API Gateway.</TD></TR>
<TR><TD><CODE>protectionDomain</CODE><BR /><I>string</I></TD><TD>protectionDomain is the name of the ScaleIO Protection Domain for the configured storage.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly 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>sslEnabled is the flag to enable/disable SSL communication with Gateway, default false</TD></TR>
<TR><TD><CODE>storageMode</CODE><BR /><I>string</I></TD><TD>storageMode indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned. Default is ThinProvisioned.</TD></TR>
<TR><TD><CODE>storagePool</CODE><BR /><I>string</I></TD><TD>storagePool is the ScaleIO Storage Pool associated with the protection domain.</TD></TR>
<TR><TD><CODE>system</CODE><BR /><I>string</I></TD><TD>system is the name of the storage system as configured in ScaleIO.</TD></TR>
<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>volumeName is the name of a volume already created in the ScaleIO system that is associated with this volume source.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="scaleiovolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ScaleIOVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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;. Default is &#34;xfs&#34;.</TD></TR>
<TR><TD><CODE>gateway</CODE><BR /><I>string</I></TD><TD>gateway is the host address of the ScaleIO API Gateway.</TD></TR>
<TR><TD><CODE>protectionDomain</CODE><BR /><I>string</I></TD><TD>protectionDomain is the name of the ScaleIO Protection Domain for the configured storage.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>readOnly 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>sslEnabled Flag enable/disable SSL communication with Gateway, default false</TD></TR>
<TR><TD><CODE>storageMode</CODE><BR /><I>string</I></TD><TD>storageMode indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned. Default is ThinProvisioned.</TD></TR>
<TR><TD><CODE>storagePool</CODE><BR /><I>string</I></TD><TD>storagePool is the ScaleIO Storage Pool associated with the protection domain.</TD></TR>
<TR><TD><CODE>system</CODE><BR /><I>string</I></TD><TD>system is the name of the storage system as configured in ScaleIO.</TD></TR>
<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>volumeName is the name of a volume already created in the ScaleIO system that is associated with this volume source.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="scheduling-v1-node-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">Scheduling</span> <span class="v">v1</span> <span class="g">node.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>node.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Scheduling</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Scheduling specifies the scheduling constraints for nodes supporting a RuntimeClass.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#runtimeclass-v1-node-k8s-io">RuntimeClass [node/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>nodeSelector</CODE><BR /><I>object</I></TD><TD>nodeSelector lists labels that must be present on nodes that support this RuntimeClass. Pods using this RuntimeClass can only be scheduled to a node matched by this selector. The RuntimeClass nodeSelector is merged with a pod&#39;s existing nodeSelector. Any conflicts will cause the pod to be rejected in admission.</TD></TR>
<TR><TD><CODE>tolerations</CODE><BR /><I><a href="#toleration-v1-core">Toleration</a> array</I></TD><TD>tolerations are appended (excluding duplicates) to pods running with this RuntimeClass during admission, effectively unioning the set of nodes tolerated by the pod and the RuntimeClass.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="scopeselector-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ScopeSelector</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="scopedresourceselectorrequirement-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ScopedResourceSelectorRequirement</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="seccompprofile-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SeccompProfile</span> <span class="v">v1</span> <span class="g">core</span></span></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>SeccompProfile</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SeccompProfile defines a pod/container&#39;s seccomp profile settings. Only one profile source may 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>
<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>localhostProfile</CODE><BR /><I>string</I></TD><TD>localhostProfile indicates a profile defined in a file on the node should be used. The profile must be preconfigured on the node to work. Must be a descending path, relative to the kubelet&#39;s configured seccomp profile location. Must be set if type is &#34;Localhost&#34;. Must NOT be set for any other type.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type indicates which kind of seccomp profile will be applied. Valid options are: Localhost - a profile defined in a file on the node should be used. RuntimeDefault - the container runtime default profile should be used. Unconfined - no profile should be applied.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="secretenvsource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SecretEnvSource</span> <span class="v">v1</span> <span class="g">core</span></span></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. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. 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>
</DIV>
<DIV class="definition-container" id="secretkeyselector-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SecretKeySelector</span> <span class="v">v1</span> <span class="g">core</span></span></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. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. 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>
</DIV>
<DIV class="definition-container" id="secretprojection-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SecretProjection</span> <span class="v">v1</span> <span class="g">core</span></span></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>items 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. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. 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>optional field specify whether the Secret or its key must be defined</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="secretreference-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SecretReference</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="secretvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SecretVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>defaultMode is Optional: mode bits used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. YAML accepts both octal and decimal values, JSON requires decimal values for mode bits. 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>items 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>optional field specify whether the Secret or its keys must be defined</TD></TR>
<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>secretName is the 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>
</DIV>
<DIV class="definition-container" id="securitycontext-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SecurityContext</span> <span class="v">v1</span> <span class="g">core</span></span></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>
<LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [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 Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<TR><TD><CODE>appArmorProfile</CODE><BR /><I><a href="#apparmorprofile-v1-core">AppArmorProfile</a></I></TD><TD>appArmorProfile is the AppArmor options to use by this container. If set, this profile overrides the pod&#39;s appArmorProfile. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<TR><TD><CODE>procMount</CODE><BR /><I>string</I></TD><TD>procMount denotes the type of proc mount to use for the containers. The default value is Default which uses the container runtime defaults for readonly paths and masked paths. This requires the ProcMountType feature flag to be enabled. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</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. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<TR><TD><CODE>seccompProfile</CODE><BR /><I><a href="#seccompprofile-v1-core">SeccompProfile</a></I></TD><TD>The seccomp options to use by this container. If seccomp options are provided at both the pod &amp; container level, the container options override the pod options. Note that this field cannot be set when spec.os.name is windows.</TD></TR>
<TR><TD><CODE>windowsOptions</CODE><BR /><I><a href="#windowssecuritycontextoptions-v1-core">WindowsSecurityContextOptions</a></I></TD><TD>The Windows specific settings applied to all containers. If unspecified, the options from the PodSecurityContext will be used. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is linux.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="selectablefield-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">SelectableField</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>SelectableField</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SelectableField specifies the JSON path of a field that may be used with field selectors.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionversion-v1-apiextensions-k8s-io">CustomResourceDefinitionVersion [apiextensions/v1]</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 which is evaluated against each custom resource to produce a field selector value. Only JSON paths without the array notation are allowed. Must point to a field of type string, boolean or integer. Types with enum values and strings with formats are allowed. If jsonPath refers to absent field in a resource, the jsonPath evaluates to an empty string. Must not point to metdata fields. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="serveraddressbyclientcidr-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">ServerAddressByClientCIDR</span> <span class="v">v1</span> <span class="g">meta</span></span></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>
</DIV>
<DIV class="definition-container" id="serverstorageversion-v1alpha1-internal-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ServerStorageVersion</span> <span class="v">v1alpha1</span> <span class="g">internal.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>internal.apiserver.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>ServerStorageVersion</CODE></TD></TR>
</TBODY>
</TABLE>
<P>An API server instance reports the version it can decode and the version it encodes objects to when persisting objects in the backend.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageversionstatus-v1alpha1-internal-apiserver-k8s-io">StorageVersionStatus [apiserverinternal/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiServerID</CODE><BR /><I>string</I></TD><TD>The ID of the reporting API server.</TD></TR>
<TR><TD><CODE>decodableVersions</CODE><BR /><I>string array</I></TD><TD>The API server can decode objects encoded in these versions. The encodingVersion must be included in the decodableVersions.</TD></TR>
<TR><TD><CODE>encodingVersion</CODE><BR /><I>string</I></TD><TD>The API server encodes the object to this version when persisting it in the backend (e.g., etcd).</TD></TR>
<TR><TD><CODE>servedVersions</CODE><BR /><I>string array</I></TD><TD>The API server can serve these versions. DecodableVersions must include all ServedVersions.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="serviceaccountsubject-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ServiceAccountSubject</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceAccountSubject</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ServiceAccountSubject holds detailed information for service-account-kind subject.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#subject-v1-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/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 matching ServiceAccount objects, or &#34;*&#34; to match regardless of name. Required.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>`namespace` is the namespace of matching ServiceAccount objects. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="serviceaccounttokenprojection-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ServiceAccountTokenProjection</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="servicebackendport-v1-networking-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ServiceBackendPort</span> <span class="v">v1</span> <span class="g">networking.k8s.io</span></span></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>ServiceBackendPort</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ServiceBackendPort is the service port being referenced.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressservicebackend-v1-networking-k8s-io">IngressServiceBackend [networking/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 port on the Service. This is a mutually exclusive setting with &#34;Number&#34;.</TD></TR>
<TR><TD><CODE>number</CODE><BR /><I>integer</I></TD><TD>number is the numerical port number (e.g. 80) on the Service. This is a mutually exclusive setting with &#34;Name&#34;.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="serviceport-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">ServicePort</span> <span class="v">v1</span> <span class="g">core</span></span></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>appProtocol</CODE><BR /><I>string</I></TD><TD>The application protocol for this port. This is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either: * Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). * Kubernetes-defined prefixed names: * &#39;kubernetes.io/h2c&#39; - HTTP/2 prior knowledge over cleartext as described in https://www.rfc-editor.org/rfc/rfc9113.html#name-starting-http-2-with-prior- * &#39;kubernetes.io/ws&#39; - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455 * &#39;kubernetes.io/wss&#39; - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455 * Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.</TD></TR>
<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. When considering the endpoints for a Service, this must match the &#39;name&#39; field in the EndpointPort. 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 is NodePort or LoadBalancer. Usually assigned by the system. If a value is specified, in-range, and not in use it will be used, otherwise the operation will fail. If not specified, a port will be allocated if this Service requires one. If this field is specified when creating a Service which does not need it, creation will fail. This field will be wiped when updating a Service to no longer need it (e.g. changing type from NodePort to ClusterIP). 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;, &#34;UDP&#34;, and &#34;SCTP&#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>
</DIV>
<DIV class="definition-container" id="servicereference-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ServiceReference</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>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-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#webhookclientconfig-v1-admissionregistration-k8s-io">WebhookClientConfig [admissionregistration/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. 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>
<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>If specified, the port on the service that hosting webhook. Default to 443 for backward compatibility. `port` should be a valid port number (1-65535, inclusive).</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="sessionaffinityconfig-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SessionAffinityConfig</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="sleepaction-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">SleepAction</span> <span class="v">v1</span> <span class="g">core</span></span></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>SleepAction</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SleepAction describes a &#34;sleep&#34; action.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#lifecyclehandler-v1-core">LifecycleHandler [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>seconds</CODE><BR /><I>integer</I></TD><TD>Seconds is the number of seconds to sleep.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="statefulsetcondition-v1-apps">
<H2 class="definition"><span class="gvk"><span class="k">StatefulSetCondition</span> <span class="v">v1</span> <span class="g">apps</span></span></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-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>
</DIV>
<DIV class="definition-container" id="statefulsetordinals-v1-apps">
<H2 class="definition"><span class="gvk"><span class="k">StatefulSetOrdinals</span> <span class="v">v1</span> <span class="g">apps</span></span></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>StatefulSetOrdinals</CODE></TD></TR>
</TBODY>
</TABLE>
<P>StatefulSetOrdinals describes the policy used for replica ordinal assignment in this StatefulSet.</P>
<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>start</CODE><BR /><I>integer</I></TD><TD>start is the number representing the first replica&#39;s index. It may be used to number replicas from an alternate index (eg: 1-indexed) over the default 0-indexed names, or to orchestrate progressive movement of replicas from one StatefulSet to another. If set, replica indices will be in the range: [.spec.ordinals.start, .spec.ordinals.start + .spec.replicas). If unset, defaults to 0. Replica indices will be in the range: [0, .spec.replicas).</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="statefulsetpersistentvolumeclaimretentionpolicy-v1-apps">
<H2 class="definition"><span class="gvk"><span class="k">StatefulSetPersistentVolumeClaimRetentionPolicy</span> <span class="v">v1</span> <span class="g">apps</span></span></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>StatefulSetPersistentVolumeClaimRetentionPolicy</CODE></TD></TR>
</TBODY>
</TABLE>
<P>StatefulSetPersistentVolumeClaimRetentionPolicy describes the policy used for PVCs created from the StatefulSet VolumeClaimTemplates.</P>
<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>whenDeleted</CODE><BR /><I>string</I></TD><TD>WhenDeleted specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is deleted. The default policy of `Retain` causes PVCs to not be affected by StatefulSet deletion. The `Delete` policy causes those PVCs to be deleted.</TD></TR>
<TR><TD><CODE>whenScaled</CODE><BR /><I>string</I></TD><TD>WhenScaled specifies what happens to PVCs created from StatefulSet VolumeClaimTemplates when the StatefulSet is scaled down. The default policy of `Retain` causes PVCs to not be affected by a scaledown. The `Delete` policy causes the associated PVCs for any excess pods above the replica count to be deleted.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="statefulsetupdatestrategy-v1-apps">
<H2 class="definition"><span class="gvk"><span class="k">StatefulSetUpdateStrategy</span> <span class="v">v1</span> <span class="g">apps</span></span></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-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>
</DIV>
<DIV class="definition-container" id="status-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">Status</span> <span class="v">v1</span> <span class="g">meta</span></span></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>
<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/sig-architecture/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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="statuscause-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">StatusCause</span> <span class="v">v1</span> <span class="g">meta</span></span></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>
</DIV>
<DIV class="definition-container" id="statusdetails-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">StatusDetails</span> <span class="v">v1</span> <span class="g">meta</span></span></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/sig-architecture/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: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="storageospersistentvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">StorageOSPersistentVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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>readOnly 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>
</DIV>
<DIV class="definition-container" id="storageosvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">StorageOSVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is the 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>readOnly 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>
</DIV>
<DIV class="definition-container" id="storageversioncondition-v1alpha1-internal-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">StorageVersionCondition</span> <span class="v">v1alpha1</span> <span class="g">internal.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>internal.apiserver.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>StorageVersionCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Describes the state of the storageVersion 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="#storageversionstatus-v1alpha1-internal-apiserver-k8s-io">StorageVersionStatus [apiserverinternal/v1alpha1]</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>observedGeneration</CODE><BR /><I>integer</I></TD><TD>If set, this represents the .metadata.generation that the condition was set based upon.</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 the condition.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="subject-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">Subject</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Subject</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Subject matches the originator of a request, as identified by the request authentication system. There are three ways of matching an originator; by user, group, or service account.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#policyruleswithsubjects-v1-flowcontrol-apiserver-k8s-io">PolicyRulesWithSubjects [flowcontrol/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>group</CODE><BR /><I><a href="#groupsubject-v1-flowcontrol-apiserver-k8s-io">GroupSubject</a></I></TD><TD>`group` matches based on user group name.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>`kind` indicates which one of the other fields is non-empty. Required</TD></TR>
<TR><TD><CODE>serviceAccount</CODE><BR /><I><a href="#serviceaccountsubject-v1-flowcontrol-apiserver-k8s-io">ServiceAccountSubject</a></I></TD><TD>`serviceAccount` matches ServiceAccounts.</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I><a href="#usersubject-v1-flowcontrol-apiserver-k8s-io">UserSubject</a></I></TD><TD>`user` matches based on username.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="subjectrulesreviewstatus-v1-authorization-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">SubjectRulesReviewStatus</span> <span class="v">v1</span> <span class="g">authorization.k8s.io</span></span></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-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>
</DIV>
<DIV class="definition-container" id="successpolicy-v1-batch">
<H2 class="definition"><span class="gvk"><span class="k">SuccessPolicy</span> <span class="v">v1</span> <span class="g">batch</span></span></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>SuccessPolicy</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SuccessPolicy describes when a Job can be declared as succeeded based on the success of some indexes.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#jobspec-v1-batch">JobSpec [batch/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#successpolicyrule-v1-batch">SuccessPolicyRule</a> array</I></TD><TD>rules represents the list of alternative rules for the declaring the Jobs as successful before `.status.succeeded &gt;= .spec.completions`. Once any of the rules are met, the &#34;SucceededCriteriaMet&#34; condition is added, and the lingering pods are removed. The terminal state for such a Job has the &#34;Complete&#34; condition. Additionally, these rules are evaluated in order; Once the Job meets one of the rules, other rules are ignored. At most 20 elements are allowed.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="successpolicyrule-v1-batch">
<H2 class="definition"><span class="gvk"><span class="k">SuccessPolicyRule</span> <span class="v">v1</span> <span class="g">batch</span></span></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>SuccessPolicyRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SuccessPolicyRule describes rule for declaring a Job as succeeded. Each rule must have at least one of the &#34;succeededIndexes&#34; or &#34;succeededCount&#34; specified.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#successpolicy-v1-batch">SuccessPolicy [batch/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>succeededCount</CODE><BR /><I>integer</I></TD><TD>succeededCount specifies the minimal required size of the actual set of the succeeded indexes for the Job. When succeededCount is used along with succeededIndexes, the check is constrained only to the set of indexes specified by succeededIndexes. For example, given that succeededIndexes is &#34;1-4&#34;, succeededCount is &#34;3&#34;, and completed indexes are &#34;1&#34;, &#34;3&#34;, and &#34;5&#34;, the Job isn&#39;t declared as succeeded because only &#34;1&#34; and &#34;3&#34; indexes are considered in that rules. When this field is null, this doesn&#39;t default to any value and is never evaluated at any time. When specified it needs to be a positive integer.</TD></TR>
<TR><TD><CODE>succeededIndexes</CODE><BR /><I>string</I></TD><TD>succeededIndexes specifies the set of indexes which need to be contained in the actual set of the succeeded indexes for the Job. The list of indexes must be within 0 to &#34;.spec.completions-1&#34; and must not contain duplicates. At least one element is required. The indexes are represented as intervals separated by commas. The intervals can be a decimal integer or a pair of decimal integers separated by a hyphen. The number are listed in represented by the first and last element of the series, separated by a hyphen. For example, if the completed indexes are 1, 3, 4, 5 and 7, they are represented as &#34;1,3-5,7&#34;. When this field is null, this field doesn&#39;t default to any value and is never evaluated at any time.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="sysctl-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">Sysctl</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="tcpsocketaction-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">TCPSocketAction</span> <span class="v">v1</span> <span class="g">core</span></span></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="#lifecyclehandler-v1-core">LifecycleHandler [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>
</DIV>
<DIV class="definition-container" id="taint-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">Taint</span> <span class="v">v1</span> <span class="g">core</span></span></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>The taint value corresponding to the taint key.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="time-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">Time</span> <span class="v">v1</span> <span class="g">meta</span></span></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="#certificatesigningrequestcondition-v1-certificates-k8s-io">CertificateSigningRequestCondition [certificates/v1]</a></LI>
<LI><a href="#condition-v1-meta">Condition [meta/v1]</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-v1-batch">CronJobStatus [batch/v1]</a></LI>
<LI><a href="#customresourcedefinitioncondition-v1-apiextensions-k8s-io">CustomResourceDefinitionCondition [apiextensions/v1]</a></LI>
<LI><a href="#daemonsetcondition-v1-apps">DaemonSetCondition [apps/v1]</a></LI>
<LI><a href="#deploymentcondition-v1-apps">DeploymentCondition [apps/v1]</a></LI>
<LI><a href="#event-v1-core">Event [core/v1]</a></LI>
<LI><a href="#event-v1-events-k8s-io">Event [events/v1]</a></LI>
<LI><a href="#flowschemacondition-v1-flowcontrol-apiserver-k8s-io">FlowSchemaCondition [flowcontrol/v1]</a></LI>
<LI><a href="#horizontalpodautoscalercondition-v2-autoscaling">HorizontalPodAutoscalerCondition [autoscaling/v2]</a></LI>
<LI><a href="#horizontalpodautoscalerstatus-v2-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2]</a></LI>
<LI><a href="#horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v1]</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="#managedfieldsentry-v1-meta">ManagedFieldsEntry [meta/v1]</a></LI>
<LI><a href="#migrationcondition-v1alpha1-storagemigration-k8s-io">MigrationCondition [storagemigration/v1alpha1]</a></LI>
<LI><a href="#namespacecondition-v1-core">NamespaceCondition [core/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="#persistentvolumestatus-v1-core">PersistentVolumeStatus [core/v1]</a></LI>
<LI><a href="#podcondition-v1-core">PodCondition [core/v1]</a></LI>
<LI><a href="#poddisruptionbudgetstatus-v1-policy">PodDisruptionBudgetStatus [policy/v1]</a></LI>
<LI><a href="#podstatus-v1-core">PodStatus [core/v1]</a></LI>
<LI><a href="#prioritylevelconfigurationcondition-v1-flowcontrol-apiserver-k8s-io">PriorityLevelConfigurationCondition [flowcontrol/v1]</a></LI>
<LI><a href="#replicasetcondition-v1-apps">ReplicaSetCondition [apps/v1]</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="#storageversioncondition-v1alpha1-internal-apiserver-k8s-io">StorageVersionCondition [apiserverinternal/v1alpha1]</a></LI>
<LI><a href="#taint-v1-core">Taint [core/v1]</a></LI>
<LI><a href="#tokenrequeststatus-v1-authentication-k8s-io">TokenRequestStatus [authentication/v1]</a></LI>
<LI><a href="#volumeerror-v1-storage-k8s-io">VolumeError [storage/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="toleration-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">Toleration</span> <span class="v">v1</span> <span class="g">core</span></span></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>
<LI><a href="#scheduling-v1-node-k8s-io">Scheduling [node/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>
</DIV>
<DIV class="definition-container" id="topologyselectorlabelrequirement-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">TopologySelectorLabelRequirement</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="topologyselectorterm-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">TopologySelectorTerm</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</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>
</DIV>
<DIV class="definition-container" id="topologyspreadconstraint-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">TopologySpreadConstraint</span> <span class="v">v1</span> <span class="g">core</span></span></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>TopologySpreadConstraint</CODE></TD></TR>
</TBODY>
</TABLE>
<P>TopologySpreadConstraint specifies how to spread matching pods among the given topology.</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>labelSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>LabelSelector is used to find matching pods. Pods that match this label selector are counted to determine the number of pods in their corresponding topology domain.</TD></TR>
<TR><TD><CODE>matchLabelKeys</CODE><BR /><I>string array</I></TD><TD>MatchLabelKeys is a set of pod label keys to select the pods over which spreading will be calculated. The keys are used to lookup values from the incoming pod labels, those key-value labels are ANDed with labelSelector to select the group of existing pods over which spreading will be calculated for the incoming pod. The same key is forbidden to exist in both MatchLabelKeys and LabelSelector. MatchLabelKeys cannot be set when LabelSelector isn&#39;t set. Keys that don&#39;t exist in the incoming pod labels will be ignored. A null or empty list means only match against labelSelector. This is a beta field and requires the MatchLabelKeysInPodTopologySpread feature gate to be enabled (enabled by default).</TD></TR>
<TR><TD><CODE>maxSkew</CODE><BR /><I>integer</I></TD><TD>MaxSkew describes the degree to which pods may be unevenly distributed. When `whenUnsatisfiable=DoNotSchedule`, it is the maximum permitted difference between the number of matching pods in the target topology and the global minimum. The global minimum is the minimum number of matching pods in an eligible domain or zero if the number of eligible domains is less than MinDomains. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 2/2/1: In this case, the global minimum is 1. | zone1 | zone2 | zone3 | | P P | P P | P | - if MaxSkew is 1, incoming pod can only be scheduled to zone3 to become 2/2/2; scheduling it onto zone1(zone2) would make the ActualSkew(3-1) on zone1(zone2) violate MaxSkew(1). - if MaxSkew is 2, incoming pod can be scheduled onto any zone. When `whenUnsatisfiable=ScheduleAnyway`, it is used to give higher precedence to topologies that satisfy it. It&#39;s a required field. Default value is 1 and 0 is not allowed.</TD></TR>
<TR><TD><CODE>minDomains</CODE><BR /><I>integer</I></TD><TD>MinDomains indicates a minimum number of eligible domains. When the number of eligible domains with matching topology keys is less than minDomains, Pod Topology Spread treats &#34;global minimum&#34; as 0, and then the calculation of Skew is performed. And when the number of eligible domains with matching topology keys equals or greater than minDomains, this value has no effect on scheduling. As a result, when the number of eligible domains is less than minDomains, scheduler won&#39;t schedule more than maxSkew Pods to those domains. If value is nil, the constraint behaves as if MinDomains is equal to 1. Valid values are integers greater than 0. When value is not nil, WhenUnsatisfiable must be DoNotSchedule. For example, in a 3-zone cluster, MaxSkew is set to 2, MinDomains is set to 5 and pods with the same labelSelector spread as 2/2/2: | zone1 | zone2 | zone3 | | P P | P P | P P | The number of domains is less than 5(MinDomains), so &#34;global minimum&#34; is treated as 0. In this situation, new pod with the same labelSelector cannot be scheduled, because computed skew will be 3(3 - 0) if new Pod is scheduled to any of the three zones, it will violate MaxSkew.</TD></TR>
<TR><TD><CODE>nodeAffinityPolicy</CODE><BR /><I>string</I></TD><TD>NodeAffinityPolicy indicates how we will treat Pod&#39;s nodeAffinity/nodeSelector when calculating pod topology spread skew. Options are: - Honor: only nodes matching nodeAffinity/nodeSelector are included in the calculations. - Ignore: nodeAffinity/nodeSelector are ignored. All nodes are included in the calculations. If this value is nil, the behavior is equivalent to the Honor policy. This is a beta-level feature default enabled by the NodeInclusionPolicyInPodTopologySpread feature flag.</TD></TR>
<TR><TD><CODE>nodeTaintsPolicy</CODE><BR /><I>string</I></TD><TD>NodeTaintsPolicy indicates how we will treat node taints when calculating pod topology spread skew. Options are: - Honor: nodes without taints, along with tainted nodes for which the incoming pod has a toleration, are included. - Ignore: node taints are ignored. All nodes are included. If this value is nil, the behavior is equivalent to the Ignore policy. This is a beta-level feature default enabled by the NodeInclusionPolicyInPodTopologySpread feature flag.</TD></TR>
<TR><TD><CODE>topologyKey</CODE><BR /><I>string</I></TD><TD>TopologyKey is the key of node labels. Nodes that have a label with this key and identical values are considered to be in the same topology. We consider each &lt;key, value&gt; as a &#34;bucket&#34;, and try to put balanced number of pods into each bucket. We define a domain as a particular instance of a topology. Also, we define an eligible domain as a domain whose nodes meet the requirements of nodeAffinityPolicy and nodeTaintsPolicy. e.g. If TopologyKey is &#34;kubernetes.io/hostname&#34;, each Node is a domain of that topology. And, if TopologyKey is &#34;topology.kubernetes.io/zone&#34;, each zone is a domain of that topology. It&#39;s a required field.</TD></TR>
<TR><TD><CODE>whenUnsatisfiable</CODE><BR /><I>string</I></TD><TD>WhenUnsatisfiable indicates how to deal with a pod if it doesn&#39;t satisfy the spread constraint. - DoNotSchedule (default) tells the scheduler not to schedule it. - ScheduleAnyway tells the scheduler to schedule the pod in any location, but giving higher precedence to topologies that would help reduce the skew. A constraint is considered &#34;Unsatisfiable&#34; for an incoming pod if and only if every possible node assignment for that pod would violate &#34;MaxSkew&#34; on some topology. For example, in a 3-zone cluster, MaxSkew is set to 1, and pods with the same labelSelector spread as 3/1/1: | zone1 | zone2 | zone3 | | P P P | P | P | If WhenUnsatisfiable is set to DoNotSchedule, incoming pod can only be scheduled to zone2(zone3) to become 3/2/1(3/1/2) as ActualSkew(2-1) on zone2(zone3) satisfies MaxSkew(1). In other words, the cluster can still be imbalanced, but scheduler won&#39;t make it *more* imbalanced. It&#39;s a required field.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="typechecking-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">TypeChecking</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>TypeChecking</CODE></TD></TR>
</TBODY>
</TABLE>
<P>TypeChecking contains results of type checking the expressions in the ValidatingAdmissionPolicy</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="#typechecking-v1beta1-admissionregistration-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="#validatingadmissionpolicystatus-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expressionWarnings</CODE><BR /><I><a href="#expressionwarning-v1-admissionregistration-k8s-io">ExpressionWarning</a> array</I></TD><TD>The type checking warnings for each expression.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="typedlocalobjectreference-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">TypedLocalObjectReference</span> <span class="v">v1</span> <span class="g">core</span></span></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>TypedLocalObjectReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>TypedLocalObjectReference contains enough information to let you locate the typed 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="#ingressbackend-v1-networking-k8s-io">IngressBackend [networking/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>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.</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>
</DIV>
<DIV class="definition-container" id="typedobjectreference-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">TypedObjectReference</span> <span class="v">v1</span> <span class="g">core</span></span></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>TypedObjectReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>TypedObjectReference contains enough information to let you locate the typed referenced object</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<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>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.</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>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of resource being referenced Note that when a namespace is specified, a gateway.networking.k8s.io/ReferenceGrant object is required in the referent namespace to allow that namespace&#39;s owner to accept the reference. See the ReferenceGrant documentation for details. (Alpha) This field requires the CrossNamespaceVolumeDataSource feature gate to be enabled.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="uncountedterminatedpods-v1-batch">
<H2 class="definition"><span class="gvk"><span class="k">UncountedTerminatedPods</span> <span class="v">v1</span> <span class="g">batch</span></span></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>UncountedTerminatedPods</CODE></TD></TR>
</TBODY>
</TABLE>
<P>UncountedTerminatedPods holds UIDs of Pods that have terminated but haven&#39;t been accounted in Job status counters.</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>failed</CODE><BR /><I>string array</I></TD><TD>failed holds UIDs of failed Pods.</TD></TR>
<TR><TD><CODE>succeeded</CODE><BR /><I>string array</I></TD><TD>succeeded holds UIDs of succeeded Pods.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="userinfo-v1-authentication-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">UserInfo</span> <span class="v">v1</span> <span class="g">authentication.k8s.io</span></span></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-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectreviewstatus-v1-authentication-k8s-io">SelfSubjectReviewStatus [authentication/v1]</a></LI>
<LI><a href="#selfsubjectreviewstatus-v1beta1-authentication-k8s-io">SelfSubjectReviewStatus [authentication/v1beta1]</a></LI>
<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>
</DIV>
<DIV class="definition-container" id="usersubject-v1-flowcontrol-apiserver-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">UserSubject</span> <span class="v">v1</span> <span class="g">flowcontrol.apiserver.k8s.io</span></span></H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>flowcontrol.apiserver.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>UserSubject</CODE></TD></TR>
</TBODY>
</TABLE>
<P>UserSubject holds detailed information for user-kind subject.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#subject-v1-flowcontrol-apiserver-k8s-io">Subject [flowcontrol/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 username that matches, or &#34;*&#34; to match all usernames. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="validatingwebhook-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ValidatingWebhook</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>ValidatingWebhook</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ValidatingWebhook 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="#validatingwebhookconfiguration-v1-admissionregistration-k8s-io">ValidatingWebhookConfiguration [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionReviewVersions</CODE><BR /><I>string array</I></TD><TD>AdmissionReviewVersions is an ordered list of preferred `AdmissionReview` versions the Webhook expects. API server will try to use first version in the list which it supports. If none of the versions specified in this list supported by API server, validation will fail for this object. If a persisted webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail and be subject to the failure policy.</TD></TR>
<TR><TD><CODE>clientConfig</CODE><BR /><I><a href="#webhookclientconfig-v1-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 Fail.</TD></TR>
<TR><TD><CODE>matchConditions</CODE><BR /><I><a href="#matchcondition-v1-admissionregistration-k8s-io">MatchCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>MatchConditions is a list of conditions that must be met for a request to be sent to this webhook. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed. The exact matching logic is (in order): 1. If ANY matchCondition evaluates to FALSE, the webhook is skipped. 2. If ALL matchConditions evaluate to TRUE, the webhook is called. 3. If any matchCondition evaluates to an error (but none are FALSE): - If failurePolicy=Fail, reject the request - If failurePolicy=Ignore, the error is ignored and the webhook is skipped</TD></TR>
<TR><TD><CODE>matchPolicy</CODE><BR /><I>string</I></TD><TD>matchPolicy defines how the &#34;rules&#34; list is used to match incoming requests. Allowed values are &#34;Exact&#34; or &#34;Equivalent&#34;. - Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the webhook. - Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the webhook. Defaults to &#34;Equivalent&#34;</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>objectSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>ObjectSelector decides whether to run the webhook based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the webhook, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#rulewithoperations-v1-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>
<TR><TD><CODE>sideEffects</CODE><BR /><I>string</I></TD><TD>SideEffects states whether this webhook has side effects. Acceptable values are: None, NoneOnDryRun (webhooks created via v1beta1 may also specify Some or Unknown). Webhooks with side effects MUST implement a reconciliation system, since a request may be rejected by a future step in the admission chain and the side effects therefore need to be undone. Requests with the dryRun attribute will be auto-rejected if they match a webhook with sideEffects == Unknown or Some.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE><BR /><I>integer</I></TD><TD>TimeoutSeconds specifies the timeout for this webhook. After the timeout passes, the webhook call will be ignored or the API call will fail based on the failure policy. The timeout value must be between 1 and 30 seconds. Default to 10 seconds.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="validation-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">Validation</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>Validation</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Validation specifies the CEL expression which is used to apply the validation.</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="#validation-v1beta1-admissionregistration-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="#validatingadmissionpolicyspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec CEL expressions have access to the contents of the API request/response, organized into CEL variables as well as some other useful variables: - &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. - &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. - &#39;request&#39; - Attributes of the API request([ref](/pkg/apis/admission/types.go#AdmissionRequest)). - &#39;params&#39; - Parameter resource referred to by the policy binding being evaluated. Only populated if the policy has a ParamKind. - &#39;namespaceObject&#39; - The namespace object that the incoming object belongs to. The value is null for cluster-scoped resources. - &#39;variables&#39; - Map of composited variables, from its name to its lazily evaluated value. For example, a variable named &#39;foo&#39; can be accessed as &#39;variables.foo&#39;. - &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request. See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz - &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the request resource. The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object. No other metadata properties are accessible. Only property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible. Accessible property names are escaped according to the following rules when accessed in the expression: - &#39;__&#39; escapes to &#39;__underscores__&#39; - &#39;.&#39; escapes to &#39;__dot__&#39; - &#39;-&#39; escapes to &#39;__dash__&#39; - &#39;/&#39; escapes to &#39;__slash__&#39; - Property names that exactly match a CEL RESERVED keyword escape to &#39;__{keyword}__&#39;. The keywords are: &#34;true&#34;, &#34;false&#34;, &#34;null&#34;, &#34;in&#34;, &#34;as&#34;, &#34;break&#34;, &#34;const&#34;, &#34;continue&#34;, &#34;else&#34;, &#34;for&#34;, &#34;function&#34;, &#34;if&#34;, &#34;import&#34;, &#34;let&#34;, &#34;loop&#34;, &#34;package&#34;, &#34;namespace&#34;, &#34;return&#34;. Examples: - Expression accessing a property named &#34;namespace&#34;: {&#34;Expression&#34;: &#34;object.__namespace__ &gt; 0&#34;} - Expression accessing a property named &#34;x-prop&#34;: {&#34;Expression&#34;: &#34;object.x__dash__prop &gt; 0&#34;} - Expression accessing a property named &#34;redact__d&#34;: {&#34;Expression&#34;: &#34;object.redact__underscores__d &gt; 0&#34;} Equality on arrays with list type of &#39;set&#39; or &#39;map&#39; ignores element order, i.e. [1, 2] == [2, 1]. Concatenation on arrays with x-kubernetes-list-type use the semantics of the list type: - &#39;set&#39;: `X + Y` performs a union where the array positions of all elements in `X` are preserved and non-intersecting elements in `Y` are appended, retaining their partial order. - &#39;map&#39;: `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the values are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` with non-intersecting keys are appended, retaining their partial order. Required.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message represents the message displayed when validation fails. The message is required if the Expression contains line breaks. The message must not contain line breaks. If unset, the message is &#34;failed rule: {Rule}&#34;. e.g. &#34;must be a URL with the host matching spec.host&#34; If the Expression contains line breaks. Message is required. The message must not contain line breaks. If unset, the message is &#34;failed Expression: {Expression}&#34;.</TD></TR>
<TR><TD><CODE>messageExpression</CODE><BR /><I>string</I></TD><TD>messageExpression declares a CEL expression that evaluates to the validation failure message that is returned when this rule fails. Since messageExpression is used as a failure message, it must evaluate to a string. If both message and messageExpression are present on a validation, then messageExpression will be used if validation fails. If messageExpression results in a runtime error, the runtime error is logged, and the validation failure message is produced as if the messageExpression field were unset. If messageExpression evaluates to an empty string, a string with only spaces, or a string that contains line breaks, then the validation failure message will also be produced as if the messageExpression field were unset, and the fact that messageExpression produced an empty string/string with only spaces/string with line breaks will be logged. messageExpression has access to all the same variables as the `expression` except for &#39;authorizer&#39; and &#39;authorizer.requestResource&#39;. Example: &#34;object.x must be less than max (&#34;+string(params.max)+&#34;)&#34;</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Reason represents a machine-readable description of why this validation failed. If this is the first validation in the list to fail, this reason, as well as the corresponding HTTP response code, are used in the HTTP response to the client. The currently supported reasons are: &#34;Unauthorized&#34;, &#34;Forbidden&#34;, &#34;Invalid&#34;, &#34;RequestEntityTooLarge&#34;. If not set, StatusReasonInvalid is used in the response to the client.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="validationrule-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">ValidationRule</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>ValidationRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ValidationRule describes a validation rule written in the CEL expression language.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#jsonschemaprops-v1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fieldPath</CODE><BR /><I>string</I></TD><TD>fieldPath represents the field path returned when the validation fails. It must be a relative JSON path (i.e. with array notation) scoped to the location of this x-kubernetes-validations extension in the schema and refer to an existing field. e.g. when validation checks if a specific attribute `foo` under a map `testMap`, the fieldPath could be set to `.testMap.foo` If the validation checks two lists must have unique attributes, the fieldPath could be set to either of the list: e.g. `.testList` It does not support list numeric index. It supports child operation to refer to an existing field currently. Refer to [JSONPath support in Kubernetes](https://kubernetes.io/docs/reference/kubectl/jsonpath/) for more info. Numeric index of array is not supported. For field name which contains special characters, use `[&#39;specialName&#39;]` to refer the field name. e.g. for attribute `foo.34$` appears in a list `testList`, the fieldPath could be set to `.testList[&#39;foo.34$&#39;]`</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message represents the message displayed when validation fails. The message is required if the Rule contains line breaks. The message must not contain line breaks. If unset, the message is &#34;failed rule: {Rule}&#34;. e.g. &#34;must be a URL with the host matching spec.host&#34;</TD></TR>
<TR><TD><CODE>messageExpression</CODE><BR /><I>string</I></TD><TD>MessageExpression declares a CEL expression that evaluates to the validation failure message that is returned when this rule fails. Since messageExpression is used as a failure message, it must evaluate to a string. If both message and messageExpression are present on a rule, then messageExpression will be used if validation fails. If messageExpression results in a runtime error, the runtime error is logged, and the validation failure message is produced as if the messageExpression field were unset. If messageExpression evaluates to an empty string, a string with only spaces, or a string that contains line breaks, then the validation failure message will also be produced as if the messageExpression field were unset, and the fact that messageExpression produced an empty string/string with only spaces/string with line breaks will be logged. messageExpression has access to all the same variables as the rule; the only difference is the return type. Example: &#34;x must be less than max (&#34;+string(self.max)+&#34;)&#34;</TD></TR>
<TR><TD><CODE>optionalOldSelf</CODE><BR /><I>boolean</I></TD><TD>optionalOldSelf is used to opt a transition rule into evaluation even when the object is first created, or if the old object is missing the value. When enabled `oldSelf` will be a CEL optional whose value will be `None` if there is no old value, or when the object is initially created. You may check for presence of oldSelf using `oldSelf.hasValue()` and unwrap it after checking using `oldSelf.value()`. Check the CEL documentation for Optional types for more information: https://pkg.go.dev/github.com/google/cel-go/cel#OptionalTypes May not be set unless `oldSelf` is used in `rule`.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason provides a machine-readable validation failure reason that is returned to the caller when a request fails this validation rule. The HTTP status code returned to the caller will match the reason of the reason of the first failed validation rule. The currently supported reasons are: &#34;FieldValueInvalid&#34;, &#34;FieldValueForbidden&#34;, &#34;FieldValueRequired&#34;, &#34;FieldValueDuplicate&#34;. If not set, default to use &#34;FieldValueInvalid&#34;. All future added reasons must be accepted by clients when reading this value and unknown reasons should be treated as FieldValueInvalid.</TD></TR>
<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>Rule represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec The Rule is scoped to the location of the x-kubernetes-validations extension in the schema. The `self` variable in the CEL expression is bound to the scoped value. Example: - Rule scoped to the root of a resource with a status subresource: {&#34;rule&#34;: &#34;self.status.actual &lt;= self.spec.maxDesired&#34;} If the Rule is scoped to an object with properties, the accessible properties of the object are field selectable via `self.field` and field presence can be checked via `has(self.field)`. Null valued fields are treated as absent fields in CEL expressions. If the Rule is scoped to an object with additionalProperties (i.e. a map) the value of the map are accessible via `self[mapKey]`, map containment can be checked via `mapKey in self` and all entries of the map are accessible via CEL macros and functions such as `self.all(...)`. If the Rule is scoped to an array, the elements of the array are accessible via `self[i]` and also by macros and functions. If the Rule is scoped to a scalar, `self` is bound to the scalar value. Examples: - Rule scoped to a map of objects: {&#34;rule&#34;: &#34;self.components[&#39;Widget&#39;].priority &lt; 10&#34;} - Rule scoped to a list of integers: {&#34;rule&#34;: &#34;self.values.all(value, value &gt;= 0 &amp;&amp; value &lt; 100)&#34;} - Rule scoped to a string value: {&#34;rule&#34;: &#34;self.startsWith(&#39;kube&#39;)&#34;} The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object and from any x-kubernetes-embedded-resource annotated objects. No other metadata properties are accessible. Unknown data preserved in custom resources via x-kubernetes-preserve-unknown-fields is not accessible in CEL expressions. This includes: - Unknown field values that are preserved by object schemas with x-kubernetes-preserve-unknown-fields. - Object properties where the property schema is of an &#34;unknown type&#34;. An &#34;unknown type&#34; is recursively defined as: - A schema with no type and x-kubernetes-preserve-unknown-fields set to true - An array where the items schema is of an &#34;unknown type&#34; - An object where the additionalProperties schema is of an &#34;unknown type&#34; Only property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible. Accessible property names are escaped according to the following rules when accessed in the expression: - &#39;__&#39; escapes to &#39;__underscores__&#39; - &#39;.&#39; escapes to &#39;__dot__&#39; - &#39;-&#39; escapes to &#39;__dash__&#39; - &#39;/&#39; escapes to &#39;__slash__&#39; - Property names that exactly match a CEL RESERVED keyword escape to &#39;__{keyword}__&#39;. The keywords are: &#34;true&#34;, &#34;false&#34;, &#34;null&#34;, &#34;in&#34;, &#34;as&#34;, &#34;break&#34;, &#34;const&#34;, &#34;continue&#34;, &#34;else&#34;, &#34;for&#34;, &#34;function&#34;, &#34;if&#34;, &#34;import&#34;, &#34;let&#34;, &#34;loop&#34;, &#34;package&#34;, &#34;namespace&#34;, &#34;return&#34;. Examples: - Rule accessing a property named &#34;namespace&#34;: {&#34;rule&#34;: &#34;self.__namespace__ &gt; 0&#34;} - Rule accessing a property named &#34;x-prop&#34;: {&#34;rule&#34;: &#34;self.x__dash__prop &gt; 0&#34;} - Rule accessing a property named &#34;redact__d&#34;: {&#34;rule&#34;: &#34;self.redact__underscores__d &gt; 0&#34;} Equality on arrays with x-kubernetes-list-type of &#39;set&#39; or &#39;map&#39; ignores element order, i.e. [1, 2] == [2, 1]. Concatenation on arrays with x-kubernetes-list-type use the semantics of the list type: - &#39;set&#39;: `X + Y` performs a union where the array positions of all elements in `X` are preserved and non-intersecting elements in `Y` are appended, retaining their partial order. - &#39;map&#39;: `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the values are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` with non-intersecting keys are appended, retaining their partial order. If `rule` makes use of the `oldSelf` variable it is implicitly a `transition rule`. By default, the `oldSelf` variable is the same type as `self`. When `optionalOldSelf` is true, the `oldSelf` variable is a CEL optional variable whose value() is the same type as `self`. See the documentation for the `optionalOldSelf` field for details. Transition rules by default are applied only on UPDATE requests and are skipped if an old value could not be found. You can opt a transition rule into unconditional evaluation by setting `optionalOldSelf` to true.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="variable-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">Variable</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>Variable</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Variable is the definition of a variable that is used for composition. A variable is defined as a named expression.</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="#variable-v1beta1-admissionregistration-k8s-io">v1beta1</a>
<a href="#variable-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="#validatingadmissionpolicyspec-v1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression is the expression that will be evaluated as the value of the variable. The CEL expression has access to the same identifiers as the CEL expressions in Validation.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the variable. The name must be a valid CEL identifier and unique among all variables. The variable can be accessed in other expressions through `variables` For example, if name is &#34;foo&#34;, the variable will be available as `variables.foo`</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="volumeattachmentsource-v1-storage-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">VolumeAttachmentSource</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>VolumeAttachmentSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>VolumeAttachmentSource represents a volume that should be attached. Right now only PersistentVolumes can be attached via external attacher, in the future we may allow also inline volumes in pods. Exactly one member can be set.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachmentspec-v1-storage-k8s-io">VolumeAttachmentSpec [storage/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>inlineVolumeSpec</CODE><BR /><I><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec</a></I></TD><TD>inlineVolumeSpec contains all the information necessary to attach a persistent volume defined by a pod&#39;s inline VolumeSource. This field is populated only for the CSIMigration feature. It contains translated fields from a pod&#39;s inline VolumeSource to a PersistentVolumeSpec. This field is beta-level and is only honored by servers that enabled the CSIMigration feature.</TD></TR>
<TR><TD><CODE>persistentVolumeName</CODE><BR /><I>string</I></TD><TD>persistentVolumeName represents the name of the persistent volume to attach.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="volumedevice-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">VolumeDevice</span> <span class="v">v1</span> <span class="g">core</span></span></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>
<LI><a href="#ephemeralcontainer-v1-core">EphemeralContainer [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>
</DIV>
<DIV class="definition-container" id="volumeerror-v1-storage-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">VolumeError</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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>v1</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-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachmentstatus-v1-storage-k8s-io">VolumeAttachmentStatus [storage/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 represents the error encountered during Attach or Detach operation. This string may be 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 represents the time the error was encountered.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="volumemount-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">VolumeMount</span> <span class="v">v1</span> <span class="g">core</span></span></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="#ephemeralcontainer-v1-core">EphemeralContainer [core/v1]</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, MountPropagationNone is used. This field is beta in 1.10. When RecursiveReadOnly is set to IfPossible or to Enabled, MountPropagation must be None or unspecified (which defaults to None).</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>recursiveReadOnly</CODE><BR /><I>string</I></TD><TD>RecursiveReadOnly specifies whether read-only mounts should be handled recursively. If ReadOnly is false, this field has no meaning and must be unspecified. If ReadOnly is true, and this field is set to Disabled, the mount is not made recursively read-only. If this field is set to IfPossible, the mount is made recursively read-only, if it is supported by the container runtime. If this field is set to Enabled, the mount is made recursively read-only if it is supported by the container runtime, otherwise the pod will not be started and an error will be generated to indicate the reason. If this field is set to IfPossible or Enabled, MountPropagation must be set to None (or be unspecified, which defaults to None). If this field is not specified, it is treated as an equivalent of Disabled.</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>
<TR><TD><CODE>subPathExpr</CODE><BR /><I>string</I></TD><TD>Expanded path within the volume from which the container&#39;s volume should be mounted. Behaves similarly to SubPath but environment variable references $(VAR_NAME) are expanded using the container&#39;s environment. Defaults to &#34;&#34; (volume&#39;s root). SubPathExpr and SubPath are mutually exclusive.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="volumenodeaffinity-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">VolumeNodeAffinity</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="volumenoderesources-v1-storage-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">VolumeNodeResources</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>VolumeNodeResources</CODE></TD></TR>
</TBODY>
</TABLE>
<P>VolumeNodeResources is a set of resource limits for scheduling of volumes.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#csinodedriver-v1-storage-k8s-io">CSINodeDriver [storage/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>count indicates the maximum number of unique volumes managed by the CSI driver that can be used on a node. A volume that is both attached and mounted on a node is considered to be used once, not twice. The same rule applies for a unique volume that is shared among multiple pods on the same node. If this field is not specified, then the supported number of volumes on this node is unbounded.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="volumeprojection-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">VolumeProjection</span> <span class="v">v1</span> <span class="g">core</span></span></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. Exactly one of these fields must be set.</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>clusterTrustBundle</CODE><BR /><I><a href="#clustertrustbundleprojection-v1-core">ClusterTrustBundleProjection</a></I></TD><TD>ClusterTrustBundle allows a pod to access the `.spec.trustBundle` field of ClusterTrustBundle objects in an auto-updating file. Alpha, gated by the ClusterTrustBundleProjection feature gate. ClusterTrustBundle objects can either be selected by name, or by the combination of signer name and a label selector. Kubelet performs aggressive normalization of the PEM contents written into the pod filesystem. Esoteric PEM features such as inter-block comments and block headers are stripped. Certificates are deduplicated. The ordering of certificates within the file is arbitrary, and Kubelet may change the order over time.</TD></TR>
<TR><TD><CODE>configMap</CODE><BR /><I><a href="#configmapprojection-v1-core">ConfigMapProjection</a></I></TD><TD>configMap 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>downwardAPI 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>secret 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>serviceAccountToken is information about the serviceAccountToken data to project</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="volumeresourcerequirements-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">VolumeResourceRequirements</span> <span class="v">v1</span> <span class="g">core</span></span></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>VolumeResourceRequirements</CODE></TD></TR>
</TBODY>
</TABLE>
<P>VolumeResourceRequirements describes the storage resource requirements for a volume.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<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-resources-containers/</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. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="vspherevirtualdiskvolumesource-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">VsphereVirtualDiskVolumeSource</span> <span class="v">v1</span> <span class="g">core</span></span></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>fsType is 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>storagePolicyID is the storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName.</TD></TR>
<TR><TD><CODE>storagePolicyName</CODE><BR /><I>string</I></TD><TD>storagePolicyName is the storage Policy Based Management (SPBM) profile name.</TD></TR>
<TR><TD><CODE>volumePath</CODE><BR /><I>string</I></TD><TD>volumePath is the path that identifies vSphere volume vmdk</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="watchevent-v1-meta">
<H2 class="definition"><span class="gvk"><span class="k">WatchEvent</span> <span class="v">v1</span> <span class="g">meta</span></span></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>
</DIV>
<DIV class="definition-container" id="webhookclientconfig-v1-admissionregistration-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">WebhookClientConfig</span> <span class="v">v1</span> <span class="g">admissionregistration.k8s.io</span></span></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>v1</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="#mutatingwebhook-v1-admissionregistration-k8s-io">MutatingWebhook [admissionregistration/v1]</a></LI>
<LI><a href="#validatingwebhook-v1-admissionregistration-k8s-io">ValidatingWebhook [admissionregistration/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 the webhook&#39;s server certificate. If unspecified, system trust roots on the apiserver are used.</TD></TR>
<TR><TD><CODE>service</CODE><BR /><I><a href="#servicereference-v1-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`.</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>
</DIV>
<DIV class="definition-container" id="webhookconversion-v1-apiextensions-k8s-io">
<H2 class="definition"><span class="gvk"><span class="k">WebhookConversion</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>WebhookConversion</CODE></TD></TR>
</TBODY>
</TABLE>
<P>WebhookConversion describes how to call a conversion webhook</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourceconversion-v1-apiextensions-k8s-io">CustomResourceConversion [apiextensions/v1]</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-v1-apiextensions-k8s-io">WebhookClientConfig</a></I></TD><TD>clientConfig is the instructions for how to call the webhook if strategy is `Webhook`.</TD></TR>
<TR><TD><CODE>conversionReviewVersions</CODE><BR /><I>string array</I></TD><TD>conversionReviewVersions is an ordered list of preferred `ConversionReview` versions the Webhook expects. The API server will use the first version in the list which it supports. If none of the versions specified in this list are supported by API server, conversion will fail for the custom resource. If a persisted Webhook configuration specifies allowed versions and does not include any versions known to the API Server, calls to the webhook will fail.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="definition-container" id="weightedpodaffinityterm-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">WeightedPodAffinityTerm</span> <span class="v">v1</span> <span class="g">core</span></span></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>
</DIV>
<DIV class="definition-container" id="windowssecuritycontextoptions-v1-core">
<H2 class="definition"><span class="gvk"><span class="k">WindowsSecurityContextOptions</span> <span class="v">v1</span> <span class="g">core</span></span></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>WindowsSecurityContextOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>WindowsSecurityContextOptions contain Windows-specific options and credentials.</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="#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>gmsaCredentialSpec</CODE><BR /><I>string</I></TD><TD>GMSACredentialSpec is where the GMSA admission webhook (https://github.com/kubernetes-sigs/windows-gmsa) inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field.</TD></TR>
<TR><TD><CODE>gmsaCredentialSpecName</CODE><BR /><I>string</I></TD><TD>GMSACredentialSpecName is the name of the GMSA credential spec to use.</TD></TR>
<TR><TD><CODE>hostProcess</CODE><BR /><I>boolean</I></TD><TD>HostProcess determines if a container should be run as a &#39;Host Process&#39; container. All of a Pod&#39;s containers must have the same effective HostProcess value (it is not allowed to have a mix of HostProcess containers and non-HostProcess containers). In addition, if HostProcess is true then HostNetwork must also be set to true.</TD></TR>
<TR><TD><CODE>runAsUserName</CODE><BR /><I>string</I></TD><TD>The UserName in Windows to run the entrypoint of the container process. Defaults to the 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>
</TBODY>
</TABLE>
</DIV>
<DIV id="old-api-versions">
<H1 class="toc-item section">Old API Versions</H1>
<P>This section contains older versions of resources shown above.</P>
</DIV>
<DIV class="resource-container" id="allocateddevicestatus-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">AllocatedDeviceStatus</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>AllocatedDeviceStatus</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="#allocateddevicestatus-v1beta1-resource-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="#resourceclaimstatus-v1alpha3-resource-k8s-io">ResourceClaimStatus [resource/v1alpha3]</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="#condition-v1-meta">Condition</a> array</I></TD><TD>Conditions contains the latest observation of the device&#39;s state. If the device has been configured according to the class and claim config references, the `Ready` condition should be True.</TD></TR>
<TR><TD><CODE>data</CODE></TD><TD>Data contains arbitrary driver-specific data. The length of the raw data must be smaller or equal to 10 Ki.</TD></TR>
<TR><TD><CODE>device</CODE><BR /><I>string</I></TD><TD>Device references one device instance via its name in the driver&#39;s resource pool. It must be a DNS label.</TD></TR>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver specifies the name of the DRA driver whose kubelet plugin should be invoked to process the allocation once the claim is needed on a node. Must be a DNS subdomain and should end with a DNS domain owned by the vendor of the driver.</TD></TR>
<TR><TD><CODE>networkData</CODE><BR /><I><a href="#networkdevicedata-v1alpha3-resource-k8s-io">NetworkDeviceData</a></I></TD><TD>NetworkData contains network-related information specific to the device.</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>This name together with the driver name and the device name field identify which device was allocated (`&lt;driver name&gt;/&lt;pool name&gt;/&lt;device name&gt;`). Must not be longer than 253 characters and may contain one or more DNS sub-domains separated by slashes.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="allocationresult-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">AllocationResult</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>AllocationResult</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="#allocationresult-v1beta1-resource-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="#resourceclaimstatus-v1alpha3-resource-k8s-io">ResourceClaimStatus [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#deviceallocationresult-v1alpha3-resource-k8s-io">DeviceAllocationResult</a></I></TD><TD>Devices is the result of allocating devices.</TD></TR>
<TR><TD><CODE>nodeSelector</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>NodeSelector defines where the allocated resources are available. If unset, they are available everywhere.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="auditannotation-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">AuditAnnotation</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>AuditAnnotation</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="#auditannotation-v1-admissionregistration-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="#validatingadmissionpolicyspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1beta1]</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>key specifies the audit annotation key. The audit annotation keys of a ValidatingAdmissionPolicy must be unique. The key must be a qualified name ([A-Za-z0-9][-A-Za-z0-9_.]*) no more than 63 bytes in length. The key is combined with the resource name of the ValidatingAdmissionPolicy to construct an audit annotation key: &#34;{ValidatingAdmissionPolicy name}/{key}&#34;. If an admission webhook uses the same resource name as this ValidatingAdmissionPolicy and the same audit annotation key, the annotation key will be identical. In this case, the first annotation written with the key will be included in the audit event and all subsequent annotations with the same key will be discarded. Required.</TD></TR>
<TR><TD><CODE>valueExpression</CODE><BR /><I>string</I></TD><TD>valueExpression represents the expression which is evaluated by CEL to produce an audit annotation value. The expression must evaluate to either a string or null value. If the expression evaluates to a string, the audit annotation is included with the string value. If the expression evaluates to null or empty string the audit annotation will be omitted. The valueExpression may be no longer than 5kb in length. If the result of the valueExpression is more than 10kb in length, it will be truncated to 10kb. If multiple ValidatingAdmissionPolicyBinding resources match an API request, then the valueExpression will be evaluated for each binding. All unique values produced by the valueExpressions will be joined together in a comma-separated list. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="basicdevice-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">BasicDevice</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>BasicDevice</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="#basicdevice-v1beta1-resource-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="#device-v1alpha3-resource-k8s-io">Device [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>attributes</CODE><BR /><I>object</I></TD><TD>Attributes defines the set of attributes for this device. The name of each attribute must be unique in that set. The maximum number of attributes and capacities combined is 32.</TD></TR>
<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>Capacity defines the set of capacities for this device. The name of each capacity must be unique in that set. The maximum number of attributes and capacities combined is 32.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="celdeviceselector-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">CELDeviceSelector</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>CELDeviceSelector</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="#celdeviceselector-v1beta1-resource-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="#deviceselector-v1alpha3-resource-k8s-io">DeviceSelector [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression is a CEL expression which evaluates a single device. It must evaluate to true when the device under consideration satisfies the desired criteria, and false when it does not. Any other result is an error and causes allocation of devices to abort. The expression&#39;s input is an object named &#34;device&#34;, which carries the following properties: - driver (string): the name of the driver which defines this device. - attributes (map[string]object): the device&#39;s attributes, grouped by prefix (e.g. device.attributes[&#34;dra.example.com&#34;] evaluates to an object with all of the attributes which were prefixed by &#34;dra.example.com&#34;. - capacity (map[string]object): the device&#39;s capacities, grouped by prefix. Example: Consider a device with driver=&#34;dra.example.com&#34;, which exposes two attributes named &#34;model&#34; and &#34;ext.example.com/family&#34; and which exposes one capacity named &#34;modules&#34;. This input to this expression would have the following fields: device.driver device.attributes[&#34;dra.example.com&#34;].model device.attributes[&#34;ext.example.com&#34;].family device.capacity[&#34;dra.example.com&#34;].modules The device.driver field can be used to check for a specific driver, either as a high-level precondition (i.e. you only want to consider devices from this driver) or as part of a multi-clause expression that is meant to consider devices from different drivers. The value type of each attribute is defined by the device definition, and users who write these expressions must consult the documentation for their specific drivers. The value type of each capacity is Quantity. If an unknown prefix is used as a lookup in either device.attributes or device.capacity, an empty map will be returned. Any reference to an unknown field will cause an evaluation error and allocation to abort. A robust expression should check for the existence of attributes before referencing them. For ease of use, the cel.bind() function is enabled, and can be used to simplify expressions that access multiple attributes with the same domain. For example: cel.bind(dra, device.attributes[&#34;dra.example.com&#34;], dra.someBool &amp;&amp; dra.anotherBool) The length of the expression must be smaller or equal to 10 Ki. The cost of evaluating it is also limited based on the estimated number of logical steps.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="crossversionobjectreference-v1-autoscaling">
<H1 class="toc-item resource"><span class="gvk"><span class="k">CrossVersionObjectReference</span> <span class="v">v1</span> <span class="g">autoscaling</span></span></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>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-v2-autoscaling">v2</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>apiVersion is the API version of the referent</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>kind is the kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the referent; More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="device-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Device</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>Device</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="#device-v1beta1-resource-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="#resourceslicespec-v1alpha3-resource-k8s-io">ResourceSliceSpec [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>basic</CODE><BR /><I><a href="#basicdevice-v1alpha3-resource-k8s-io">BasicDevice</a></I></TD><TD>Basic defines one device instance.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is unique identifier among all devices managed by the driver in the pool. It must be a DNS label.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="deviceallocationconfiguration-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceAllocationConfiguration</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceAllocationConfiguration</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="#deviceallocationconfiguration-v1beta1-resource-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="#deviceallocationresult-v1alpha3-resource-k8s-io">DeviceAllocationResult [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>opaque</CODE><BR /><I><a href="#opaquedeviceconfiguration-v1alpha3-resource-k8s-io">OpaqueDeviceConfiguration</a></I></TD><TD>Opaque provides driver-specific configuration parameters.</TD></TR>
<TR><TD><CODE>requests</CODE><BR /><I>string array</I></TD><TD>Requests lists the names of requests where the configuration applies. If empty, its applies to all requests.</TD></TR>
<TR><TD><CODE>source</CODE><BR /><I>string</I></TD><TD>Source records whether the configuration comes from a class and thus is not something that a normal user would have been able to set or from a claim.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="deviceallocationresult-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceAllocationResult</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceAllocationResult</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="#deviceallocationresult-v1beta1-resource-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="#allocationresult-v1alpha3-resource-k8s-io">AllocationResult [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>config</CODE><BR /><I><a href="#deviceallocationconfiguration-v1alpha3-resource-k8s-io">DeviceAllocationConfiguration</a> array</I></TD><TD>This field is a combination of all the claim and class configuration parameters. Drivers can distinguish between those based on a flag. This includes configuration parameters for drivers which have no allocated devices in the result because it is up to the drivers which configuration parameters they support. They can silently ignore unknown configuration parameters.</TD></TR>
<TR><TD><CODE>results</CODE><BR /><I><a href="#devicerequestallocationresult-v1alpha3-resource-k8s-io">DeviceRequestAllocationResult</a> array</I></TD><TD>Results lists all allocated devices.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="deviceattribute-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceAttribute</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceAttribute</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="#deviceattribute-v1beta1-resource-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="#basicdevice-v1alpha3-resource-k8s-io">BasicDevice [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>bool</CODE><BR /><I>boolean</I></TD><TD>BoolValue is a true/false value.</TD></TR>
<TR><TD><CODE>int</CODE><BR /><I>integer</I></TD><TD>IntValue is a number.</TD></TR>
<TR><TD><CODE>string</CODE><BR /><I>string</I></TD><TD>StringValue is a string. Must not be longer than 64 characters.</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>VersionValue is a semantic version according to semver.org spec 2.0.0. Must not be longer than 64 characters.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="deviceclaim-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceClaim</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceClaim</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="#deviceclaim-v1beta1-resource-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="#resourceclaimspec-v1alpha3-resource-k8s-io">ResourceClaimSpec [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>config</CODE><BR /><I><a href="#deviceclaimconfiguration-v1alpha3-resource-k8s-io">DeviceClaimConfiguration</a> array</I></TD><TD>This field holds configuration for multiple potential drivers which could satisfy requests in this claim. It is ignored while allocating the claim.</TD></TR>
<TR><TD><CODE>constraints</CODE><BR /><I><a href="#deviceconstraint-v1alpha3-resource-k8s-io">DeviceConstraint</a> array</I></TD><TD>These constraints must be satisfied by the set of devices that get allocated for the claim.</TD></TR>
<TR><TD><CODE>requests</CODE><BR /><I><a href="#devicerequest-v1alpha3-resource-k8s-io">DeviceRequest</a> array</I></TD><TD>Requests represent individual requests for distinct devices which must all be satisfied. If empty, nothing needs to be allocated.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="deviceclaimconfiguration-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceClaimConfiguration</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceClaimConfiguration</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="#deviceclaimconfiguration-v1beta1-resource-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="#deviceclaim-v1alpha3-resource-k8s-io">DeviceClaim [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>opaque</CODE><BR /><I><a href="#opaquedeviceconfiguration-v1alpha3-resource-k8s-io">OpaqueDeviceConfiguration</a></I></TD><TD>Opaque provides driver-specific configuration parameters.</TD></TR>
<TR><TD><CODE>requests</CODE><BR /><I>string array</I></TD><TD>Requests lists the names of requests where the configuration applies. If empty, it applies to all requests.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="deviceclass-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceClass</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceClass</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="#deviceclass-v1beta1-resource-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="#deviceclasslist-v1alpha3-resource-k8s-io">DeviceClassList [resource/v1alpha3]</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/sig-architecture/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/sig-architecture/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="#deviceclassspec-v1alpha3-resource-k8s-io">DeviceClassSpec</a></I></TD><TD>Spec defines what can be allocated and how to configure it. This is mutable. Consumers have to be prepared for classes changing at any time, either because they get updated or replaced. Claim allocations are done once based on whatever was set in classes at the time of allocation. Changing the spec automatically increments the metadata.generation number.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="deviceclassspec-v1alpha3-resource-k8s-io">DeviceClassSpec v1alpha3 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>config</CODE><BR /><I><a href="#deviceclassconfiguration-v1alpha3-resource-k8s-io">DeviceClassConfiguration</a> array</I></TD><TD>Config defines configuration parameters that apply to each device that is claimed via this class. Some classses may potentially be satisfied by multiple drivers, so each instance of a vendor configuration applies to exactly one driver. They are passed to the driver, but are not considered while allocating the claim.</TD></TR>
<TR><TD><CODE>selectors</CODE><BR /><I><a href="#deviceselector-v1alpha3-resource-k8s-io">DeviceSelector</a> array</I></TD><TD>Each selector must be satisfied by a device which is claimed via this class.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="deviceclasslist-v1alpha3-resource-k8s-io">DeviceClassList v1alpha3 resource</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a> array</I></TD><TD>Items is the list of resource classes.</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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/resource.k8s.io/v1alpha3/deviceclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1alpha3/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1alpha3/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1alpha3/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1alpha3/deviceclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deviceclass-v1alpha3-resource-k8s-io">DeviceClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind DeviceClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/deviceclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deviceclasslist-v1alpha3-resource-k8s-io">DeviceClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind DeviceClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/deviceclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeviceClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-deviceclass-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of DeviceClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/deviceclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="deviceclassconfiguration-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceClassConfiguration</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceClassConfiguration</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="#deviceclassconfiguration-v1beta1-resource-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="#deviceclassspec-v1alpha3-resource-k8s-io">DeviceClassSpec [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>opaque</CODE><BR /><I><a href="#opaquedeviceconfiguration-v1alpha3-resource-k8s-io">OpaqueDeviceConfiguration</a></I></TD><TD>Opaque provides driver-specific configuration parameters.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="deviceconstraint-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceConstraint</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceConstraint</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="#deviceconstraint-v1beta1-resource-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="#deviceclaim-v1alpha3-resource-k8s-io">DeviceClaim [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>matchAttribute</CODE><BR /><I>string</I></TD><TD>MatchAttribute requires that all devices in question have this attribute and that its type and value are the same across those devices. For example, if you specified &#34;dra.example.com/numa&#34; (a hypothetical example!), then only devices in the same NUMA node will be chosen. A device which does not have that attribute will not be chosen. All devices should use a value of the same type for this attribute because that is part of its specification, but if one device doesn&#39;t, then it also will not be chosen. Must include the domain qualifier.</TD></TR>
<TR><TD><CODE>requests</CODE><BR /><I>string array</I></TD><TD>Requests is a list of the one or more requests in this claim which must co-satisfy this constraint. If a request is fulfilled by multiple devices, then all of the devices must satisfy the constraint. If this is not specified, this constraint applies to all requests in this claim.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="devicerequest-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceRequest</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceRequest</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="#devicerequest-v1beta1-resource-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="#deviceclaim-v1alpha3-resource-k8s-io">DeviceClaim [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>adminAccess</CODE><BR /><I>boolean</I></TD><TD>AdminAccess indicates that this is a claim for administrative access to the device(s). Claims with AdminAccess are expected to be used for monitoring or other management services for a device. They ignore all ordinary claims to the device with respect to access modes and any resource allocations. This is an alpha field and requires enabling the DRAAdminAccess feature gate. Admin access is disabled if this field is unset or set to false, otherwise it is enabled.</TD></TR>
<TR><TD><CODE>allocationMode</CODE><BR /><I>string</I></TD><TD>AllocationMode and its related fields define how devices are allocated to satisfy this request. Supported values are: - ExactCount: This request is for a specific number of devices. This is the default. The exact number is provided in the count field. - All: This request is for all of the matching devices in a pool. Allocation will fail if some devices are already allocated, unless adminAccess is requested. If AlloctionMode is not specified, the default mode is ExactCount. If the mode is ExactCount and count is not specified, the default count is one. Any other requests must specify this field. More modes may get added in the future. Clients must refuse to handle requests with unknown modes.</TD></TR>
<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>Count is used only when the count mode is &#34;ExactCount&#34;. Must be greater than zero. If AllocationMode is ExactCount and this field is not specified, the default is one.</TD></TR>
<TR><TD><CODE>deviceClassName</CODE><BR /><I>string</I></TD><TD>DeviceClassName references a specific DeviceClass, which can define additional configuration and selectors to be inherited by this request. A class is required. Which classes are available depends on the cluster. Administrators may use this to restrict which devices may get requested by only installing classes with selectors for permitted devices. If users are free to request anything without restrictions, then administrators can create an empty DeviceClass for users to reference.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name can be used to reference this request in a pod.spec.containers[].resources.claims entry and in a constraint of the claim. Must be a DNS label.</TD></TR>
<TR><TD><CODE>selectors</CODE><BR /><I><a href="#deviceselector-v1alpha3-resource-k8s-io">DeviceSelector</a> array</I></TD><TD>Selectors define criteria which must be satisfied by a specific device in order for that device to be considered for this request. All selectors must be satisfied for a device to be considered.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="devicerequestallocationresult-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceRequestAllocationResult</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceRequestAllocationResult</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="#devicerequestallocationresult-v1beta1-resource-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="#deviceallocationresult-v1alpha3-resource-k8s-io">DeviceAllocationResult [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>adminAccess</CODE><BR /><I>boolean</I></TD><TD>AdminAccess indicates that this device was allocated for administrative access. See the corresponding request field for a definition of mode. This is an alpha field and requires enabling the DRAAdminAccess feature gate. Admin access is disabled if this field is unset or set to false, otherwise it is enabled.</TD></TR>
<TR><TD><CODE>device</CODE><BR /><I>string</I></TD><TD>Device references one device instance via its name in the driver&#39;s resource pool. It must be a DNS label.</TD></TR>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver specifies the name of the DRA driver whose kubelet plugin should be invoked to process the allocation once the claim is needed on a node. Must be a DNS subdomain and should end with a DNS domain owned by the vendor of the driver.</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>This name together with the driver name and the device name field identify which device was allocated (`&lt;driver name&gt;/&lt;pool name&gt;/&lt;device name&gt;`). Must not be longer than 253 characters and may contain one or more DNS sub-domains separated by slashes.</TD></TR>
<TR><TD><CODE>request</CODE><BR /><I>string</I></TD><TD>Request is the name of the request in the claim which caused this device to be allocated. Multiple devices may have been allocated per request.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="deviceselector-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">DeviceSelector</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>DeviceSelector</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="#deviceselector-v1beta1-resource-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="#deviceclassspec-v1alpha3-resource-k8s-io">DeviceClassSpec [resource/v1alpha3]</a></LI>
<LI><a href="#devicerequest-v1alpha3-resource-k8s-io">DeviceRequest [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>cel</CODE><BR /><I><a href="#celdeviceselector-v1alpha3-resource-k8s-io">CELDeviceSelector</a></I></TD><TD>CEL contains a CEL expression for selecting a device.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="endpointport-v1-discovery-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">EndpointPort</span> <span class="v">v1</span> <span class="g">discovery.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>discovery.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointPort</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="#endpointslice-v1-discovery-k8s-io">EndpointSlice [discovery/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>appProtocol</CODE><BR /><I>string</I></TD><TD>The application protocol for this port. This is used as a hint for implementations to offer richer behavior for protocols that they understand. This field follows standard Kubernetes label syntax. Valid values are either: * Un-prefixed protocol names - reserved for IANA standard service names (as per RFC-6335 and https://www.iana.org/assignments/service-names). * Kubernetes-defined prefixed names: * &#39;kubernetes.io/h2c&#39; - HTTP/2 prior knowledge over cleartext as described in https://www.rfc-editor.org/rfc/rfc9113.html#name-starting-http-2-with-prior- * &#39;kubernetes.io/ws&#39; - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455 * &#39;kubernetes.io/wss&#39; - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455 * Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name represents the name of this port. All ports in an EndpointSlice must have a unique name. If the EndpointSlice is derived from a Kubernetes service, this corresponds to the Service.ports[].name. Name must either be an empty string or pass DNS_LABEL validation: * must be no more than 63 characters long. * must consist of lower case alphanumeric characters or &#39;-&#39;. * must start and end with an alphanumeric character. Default is empty string.</TD></TR>
<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>port represents the port number of the endpoint. If this is not specified, ports are not restricted and must be interpreted in the context of the specific consumer.</TD></TR>
<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>protocol represents the IP protocol for this port. Must be UDP, TCP, or SCTP. Default is TCP.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="event-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Event</span> <span class="v">v1</span> <span class="g">core</span></span></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-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/sig-architecture/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/sig-architecture/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/sig-architecture/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>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-event-v1-core">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-event-v1-core">
<H2 class="toc-item operation">Create</H2>
<P>create an Event</P>
<H3>HTTP Request</H3>
<p><CODE>POST /api/v1/namespaces/{namespace}/events</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-event-v1-core">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified Event</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /api/v1/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-event-v1-core">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified Event</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /api/v1/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-event-v1-core">
<H2 class="toc-item operation">Delete</H2>
<P>delete an Event</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-event-v1-core">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of Event</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /api/v1/namespaces/{namespace}/events</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-event-v1-core">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-event-v1-core">
<H2 class="toc-item operation">Read</H2>
<P>read the specified Event</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-event-v1-core">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind Event</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/namespaces/{namespace}/events</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-event-v1-core">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind Event</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/events</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-event-v1-core">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind Event. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/events/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-event-v1-core">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/namespaces/{namespace}/events</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-event-v1-core">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Event. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /api/v1/watch/events</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="eventseries-v1-core">
<H1 class="toc-item resource"><span class="gvk"><span class="k">EventSeries</span> <span class="v">v1</span> <span class="g">core</span></span></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>EventSeries</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="#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>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="expressionwarning-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ExpressionWarning</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>ExpressionWarning</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="#expressionwarning-v1-admissionregistration-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="#typechecking-v1beta1-admissionregistration-k8s-io">TypeChecking [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fieldRef</CODE><BR /><I>string</I></TD><TD>The path to the field that refers the expression. For example, the reference to the expression of the first item of validations is &#34;spec.validations[0].expression&#34;</TD></TR>
<TR><TD><CODE>warning</CODE><BR /><I>string</I></TD><TD>The content of type checking information in a human-readable form. Each line of the warning contains the type that the expression is checked against, followed by the type check error from the compiler.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="horizontalpodautoscaler-v1-autoscaling">
<H1 class="toc-item resource"><span class="gvk"><span class="k">HorizontalPodAutoscaler</span> <span class="v">v1</span> <span class="g">autoscaling</span></span></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-v2-autoscaling">v2</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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#horizontalpodautoscalerspec-v1-autoscaling">HorizontalPodAutoscalerSpec</a></I></TD><TD>spec defines the behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/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>status is the current information about the autoscaler.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" 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>maxReplicas is the 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>minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down. It defaults to 1 pod. minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured. Scaling is active as long as at least one metric value is available.</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>targetCPUUtilizationPercentage is the 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 class="inline-definition" 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>currentCPUUtilizationPercentage is the 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>currentReplicas is the current number of replicas of pods managed by this 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.</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 class="inline-definition" 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#horizontalpodautoscaler-v1-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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Create</H2>
<P>create a HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>202<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
<DIV class="operation-container" id="delete-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Delete</H2>
<P>delete a HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Read</H2>
<P>read the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v1/horizontalpodautoscalers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v1/watch/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE></P>
<H3>Path 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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v1/watch/namespaces/{namespace}/horizontalpodautoscalers</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of HorizontalPodAutoscaler. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v1/watch/horizontalpodautoscalers</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="replace-status-horizontalpodautoscaler-v1-autoscaling">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE></P>
<H3>Path 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="matchcondition-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">MatchCondition</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>MatchCondition</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="#matchcondition-v1-admissionregistration-k8s-io">v1</a>
<a href="#matchcondition-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="#validatingadmissionpolicyspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables: &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. &#39;request&#39; - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request. See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the request resource. Documentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/ Required.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;, and must start and end with an alphanumeric character (e.g. &#39;MyName&#39;, or &#39;my.name&#39;, or &#39;123-abc&#39;, regex used for validation is &#39;([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]&#39;) with an optional DNS subdomain prefix and &#39;/&#39; (e.g. &#39;example.com/MyName&#39;) Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="matchcondition-v1alpha1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">MatchCondition</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>MatchCondition</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="#matchcondition-v1-admissionregistration-k8s-io">v1</a>
<a href="#matchcondition-v1beta1-admissionregistration-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="#mutatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicySpec [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression represents the expression which will be evaluated by CEL. Must evaluate to bool. CEL expressions have access to the contents of the AdmissionRequest and Authorizer, organized into CEL variables: &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. &#39;request&#39; - Attributes of the admission request(/pkg/apis/admission/types.go#AdmissionRequest). &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request. See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the request resource. Documentation on CEL: https://kubernetes.io/docs/reference/using-api/cel/ Required.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is an identifier for this match condition, used for strategic merging of MatchConditions, as well as providing an identifier for logging purposes. A good name should be descriptive of the associated expression. Name must be a qualified name consisting of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;, and must start and end with an alphanumeric character (e.g. &#39;MyName&#39;, or &#39;my.name&#39;, or &#39;123-abc&#39;, regex used for validation is &#39;([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]&#39;) with an optional DNS subdomain prefix and &#39;/&#39; (e.g. &#39;example.com/MyName&#39;) Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="matchresources-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">MatchResources</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>MatchResources</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="#matchresources-v1-admissionregistration-k8s-io">v1</a>
<a href="#matchresources-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="#validatingadmissionpolicybindingspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec [admissionregistration/v1beta1]</a></LI>
<LI><a href="#validatingadmissionpolicyspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>excludeResourceRules</CODE><BR /><I><a href="#namedrulewithoperations-v1beta1-admissionregistration-k8s-io">NamedRuleWithOperations</a> array</I></TD><TD>ExcludeResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy should not care about. The exclude rules take precedence over include rules (if a resource matches both, it is excluded)</TD></TR>
<TR><TD><CODE>matchPolicy</CODE><BR /><I>string</I></TD><TD>matchPolicy defines how the &#34;MatchResources&#34; list is used to match incoming requests. Allowed values are &#34;Exact&#34; or &#34;Equivalent&#34;. - Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the ValidatingAdmissionPolicy. - Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the ValidatingAdmissionPolicy. Defaults to &#34;Equivalent&#34;</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 admission control policy 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 policy. 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 policy 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>objectSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>ObjectSelector decides whether to run the validation based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the cel validation, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.</TD></TR>
<TR><TD><CODE>resourceRules</CODE><BR /><I><a href="#namedrulewithoperations-v1beta1-admissionregistration-k8s-io">NamedRuleWithOperations</a> array</I></TD><TD>ResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy matches. The policy cares about an operation if it matches _any_ Rule.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="matchresources-v1alpha1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">MatchResources</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>MatchResources</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="#matchresources-v1-admissionregistration-k8s-io">v1</a>
<a href="#matchresources-v1beta1-admissionregistration-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="#mutatingadmissionpolicybindingspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBindingSpec [admissionregistration/v1alpha1]</a></LI>
<LI><a href="#mutatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicySpec [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>excludeResourceRules</CODE><BR /><I><a href="#namedrulewithoperations-v1alpha1-admissionregistration-k8s-io">NamedRuleWithOperations</a> array</I></TD><TD>ExcludeResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy should not care about. The exclude rules take precedence over include rules (if a resource matches both, it is excluded)</TD></TR>
<TR><TD><CODE>matchPolicy</CODE><BR /><I>string</I></TD><TD>matchPolicy defines how the &#34;MatchResources&#34; list is used to match incoming requests. Allowed values are &#34;Exact&#34; or &#34;Equivalent&#34;. - Exact: match a request only if it exactly matches a specified rule. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, but &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would not be sent to the ValidatingAdmissionPolicy. - Equivalent: match a request if modifies a resource listed in rules, even via another API group or version. For example, if deployments can be modified via apps/v1, apps/v1beta1, and extensions/v1beta1, and &#34;rules&#34; only included `apiGroups:[&#34;apps&#34;], apiVersions:[&#34;v1&#34;], resources: [&#34;deployments&#34;]`, a request to apps/v1beta1 or extensions/v1beta1 would be converted to apps/v1 and sent to the ValidatingAdmissionPolicy. Defaults to &#34;Equivalent&#34;</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 admission control policy 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 policy. 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 policy 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>objectSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>ObjectSelector decides whether to run the validation based on if the object has matching labels. objectSelector is evaluated against both the oldObject and newObject that would be sent to the cel validation, and is considered to match if either object matches the selector. A null object (oldObject in the case of create, or newObject in the case of delete) or an object that cannot have labels (like a DeploymentRollback or a PodProxyOptions object) is not considered to match. Use the object selector only if the webhook is opt-in, because end users may skip the admission webhook by setting the labels. Default to the empty LabelSelector, which matches everything.</TD></TR>
<TR><TD><CODE>resourceRules</CODE><BR /><I><a href="#namedrulewithoperations-v1alpha1-admissionregistration-k8s-io">NamedRuleWithOperations</a> array</I></TD><TD>ResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy matches. The policy cares about an operation if it matches _any_ Rule.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="namedrulewithoperations-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">NamedRuleWithOperations</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>NamedRuleWithOperations</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="#namedrulewithoperations-v1-admissionregistration-k8s-io">v1</a>
<a href="#namedrulewithoperations-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="#matchresources-v1beta1-admissionregistration-k8s-io">MatchResources [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, DELETE, CONNECT or * for all of those operations and any future admission operations that are added. If &#39;\*&#39; is present, the length of the slice must be one. Required.</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. 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>
<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>scope specifies the scope of this rule. Valid values are &#34;Cluster&#34;, &#34;Namespaced&#34;, and &#34;*&#34; &#34;Cluster&#34; means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. &#34;Namespaced&#34; means that only namespaced resources will match this rule. &#34;*&#34; means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is &#34;*&#34;.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="namedrulewithoperations-v1alpha1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">NamedRuleWithOperations</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>NamedRuleWithOperations</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="#namedrulewithoperations-v1-admissionregistration-k8s-io">v1</a>
<a href="#namedrulewithoperations-v1beta1-admissionregistration-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="#matchresources-v1alpha1-admissionregistration-k8s-io">MatchResources [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>operations</CODE><BR /><I>string array</I></TD><TD>Operations is the operations the admission hook cares about - CREATE, UPDATE, DELETE, CONNECT or * for all of those operations and any future admission operations that are added. If &#39;\*&#39; is present, the length of the slice must be one. Required.</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. 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>
<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>scope specifies the scope of this rule. Valid values are &#34;Cluster&#34;, &#34;Namespaced&#34;, and &#34;*&#34; &#34;Cluster&#34; means that only cluster-scoped resources will match this rule. Namespace API objects are cluster-scoped. &#34;Namespaced&#34; means that only namespaced resources will match this rule. &#34;*&#34; means that there are no scope restrictions. Subresources match the scope of their parent resource. Default is &#34;*&#34;.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="networkdevicedata-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">NetworkDeviceData</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>NetworkDeviceData</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="#networkdevicedata-v1beta1-resource-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="#allocateddevicestatus-v1alpha3-resource-k8s-io">AllocatedDeviceStatus [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>hardwareAddress</CODE><BR /><I>string</I></TD><TD>HardwareAddress represents the hardware address (e.g. MAC Address) of the device&#39;s network interface. Must not be longer than 128 characters.</TD></TR>
<TR><TD><CODE>interfaceName</CODE><BR /><I>string</I></TD><TD>InterfaceName specifies the name of the network interface associated with the allocated device. This might be the name of a physical or virtual network interface being configured in the pod. Must not be longer than 256 characters.</TD></TR>
<TR><TD><CODE>ips</CODE><BR /><I>string array</I></TD><TD>IPs lists the network addresses assigned to the device&#39;s network interface. This can include both IPv4 and IPv6 addresses. The IPs are in the CIDR notation, which includes both the address and the associated subnet mask. e.g.: &#34;192.0.2.5/24&#34; for IPv4 and &#34;2001:db8::5/64&#34; for IPv6.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="opaquedeviceconfiguration-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">OpaqueDeviceConfiguration</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>OpaqueDeviceConfiguration</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="#opaquedeviceconfiguration-v1beta1-resource-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="#deviceallocationconfiguration-v1alpha3-resource-k8s-io">DeviceAllocationConfiguration [resource/v1alpha3]</a></LI>
<LI><a href="#deviceclaimconfiguration-v1alpha3-resource-k8s-io">DeviceClaimConfiguration [resource/v1alpha3]</a></LI>
<LI><a href="#deviceclassconfiguration-v1alpha3-resource-k8s-io">DeviceClassConfiguration [resource/v1alpha3]</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 used to determine which kubelet plugin needs to be passed these configuration parameters. An admission policy provided by the driver developer could use this to decide whether it needs to validate them. Must be a DNS subdomain and should end with a DNS domain owned by the vendor of the driver.</TD></TR>
<TR><TD><CODE>parameters</CODE></TD><TD>Parameters can contain arbitrary data. It is the responsibility of the driver developer to handle validation and versioning. Typically this includes self-identification and a version (&#34;kind&#34; + &#34;apiVersion&#34; for Kubernetes types), with conversion between different versions. The length of the raw data must be smaller or equal to 10 Ki.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="paramkind-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ParamKind</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>ParamKind</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="#paramkind-v1-admissionregistration-k8s-io">v1</a>
<a href="#paramkind-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="#validatingadmissionpolicyspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [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 is the API group version the resources belong to. In format of &#34;group/version&#34;. Required.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the API kind the resources belong to. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="paramkind-v1alpha1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ParamKind</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>ParamKind</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="#paramkind-v1-admissionregistration-k8s-io">v1</a>
<a href="#paramkind-v1beta1-admissionregistration-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="#mutatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicySpec [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 is the API group version the resources belong to. In format of &#34;group/version&#34;. Required.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the API kind the resources belong to. Required.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="paramref-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ParamRef</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>ParamRef</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="#paramref-v1-admissionregistration-k8s-io">v1</a>
<a href="#paramref-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="#validatingadmissionpolicybindingspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec [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 resource being referenced. One of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset. A single parameter used for all admission requests can be configured by setting the `name` field, leaving `selector` blank, and setting namespace if `paramKind` is namespace-scoped.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>namespace is the namespace of the referenced resource. Allows limiting the search for params to a specific namespace. Applies to both `name` and `selector` fields. A per-namespace parameter may be used by specifying a namespace-scoped `paramKind` in the policy and leaving this field empty. - If `paramKind` is cluster-scoped, this field MUST be unset. Setting this field results in a configuration error. - If `paramKind` is namespace-scoped, the namespace of the object being evaluated for admission will be used when this field is left unset. Take care that if this is left empty the binding must not match any cluster-scoped resources, which will result in an error.</TD></TR>
<TR><TD><CODE>parameterNotFoundAction</CODE><BR /><I>string</I></TD><TD>`parameterNotFoundAction` controls the behavior of the binding when the resource exists, and name or selector is valid, but there are no parameters matched by the binding. If the value is set to `Allow`, then no matched parameters will be treated as successful validation by the binding. If set to `Deny`, then no matched parameters will be subject to the `failurePolicy` of the policy. Allowed values are `Allow` or `Deny` Required</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector can be used to match multiple param objects based on their labels. Supply selector: {} to match all resources of the ParamKind. If multiple params are found, they are all evaluated with the policy expressions and the results are ANDed together. One of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="paramref-v1alpha1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ParamRef</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>ParamRef</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="#paramref-v1-admissionregistration-k8s-io">v1</a>
<a href="#paramref-v1beta1-admissionregistration-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="#mutatingadmissionpolicybindingspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicyBindingSpec [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 name of the resource being referenced. `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>namespace is the namespace of the referenced resource. Allows limiting the search for params to a specific namespace. Applies to both `name` and `selector` fields. A per-namespace parameter may be used by specifying a namespace-scoped `paramKind` in the policy and leaving this field empty. - If `paramKind` is cluster-scoped, this field MUST be unset. Setting this field results in a configuration error. - If `paramKind` is namespace-scoped, the namespace of the object being evaluated for admission will be used when this field is left unset. Take care that if this is left empty the binding must not match any cluster-scoped resources, which will result in an error.</TD></TR>
<TR><TD><CODE>parameterNotFoundAction</CODE><BR /><I>string</I></TD><TD>`parameterNotFoundAction` controls the behavior of the binding when the resource exists, and name or selector is valid, but there are no parameters matched by the binding. If the value is set to `Allow`, then no matched parameters will be treated as successful validation by the binding. If set to `Deny`, then no matched parameters will be subject to the `failurePolicy` of the policy. Allowed values are `Allow` or `Deny` Default to `Deny`</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector can be used to match multiple param objects based on their labels. Supply selector: {} to match all resources of the ParamKind. If multiple params are found, they are all evaluated with the policy expressions and the results are ANDed together. One of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="resourceclaim-v1beta1-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourceClaim</span> <span class="v">v1beta1</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ResourceClaim</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="#resourceclaim-v1-core">v1</a>
<a href="#resourceclaim-v1alpha3-resource-k8s-io">v1alpha3</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaimlist-v1beta1-resource-k8s-io">ResourceClaimList [resource/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/sig-architecture/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/sig-architecture/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="#resourceclaimspec-v1beta1-resource-k8s-io">ResourceClaimSpec</a></I></TD><TD>Spec describes what is being requested and how to configure it. The spec is immutable.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#resourceclaimstatus-v1beta1-resource-k8s-io">ResourceClaimStatus</a></I></TD><TD>Status describes whether the claim is ready to use and what has been allocated.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="resourceclaimspec-v1beta1-resource-k8s-io">ResourceClaimSpec v1beta1 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim [resource/v1beta1]</a></LI>
<LI><a href="#resourceclaimtemplatespec-v1beta1-resource-k8s-io">ResourceClaimTemplateSpec [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#deviceclaim-v1beta1-resource-k8s-io">DeviceClaim</a></I></TD><TD>Devices defines how to request devices.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceclaimstatus-v1beta1-resource-k8s-io">ResourceClaimStatus v1beta1 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim [resource/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allocation</CODE><BR /><I><a href="#allocationresult-v1beta1-resource-k8s-io">AllocationResult</a></I></TD><TD>Allocation is set once the claim has been allocated successfully.</TD></TR>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#allocateddevicestatus-v1beta1-resource-k8s-io">AllocatedDeviceStatus</a> array</I></TD><TD>Devices contains the status of each device allocated for this claim, as reported by the driver. This can include driver-specific information. Entries are owned by their respective drivers.</TD></TR>
<TR><TD><CODE>reservedFor</CODE><BR /><I><a href="#resourceclaimconsumerreference-v1beta1-resource-k8s-io">ResourceClaimConsumerReference</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>uid</I></TD><TD>ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started. A claim that is in use or might be in use because it has been reserved must not get deallocated. In a cluster with multiple scheduler instances, two pods might get scheduled concurrently by different schedulers. When they reference the same ResourceClaim which already has reached its maximum number of consumers, only one pod can be scheduled. Both schedulers try to add their pod to the claim.status.reservedFor field, but only the update that reaches the API server first gets stored. The other one fails with an error and the scheduler which issued it knows that it must put the pod back into the queue, waiting for the ResourceClaim to become usable again. There can be at most 32 such reservations. This may get increased in the future, but not reduced.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceclaimlist-v1beta1-resource-k8s-io">ResourceClaimList v1beta1 resource</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a> array</I></TD><TD>Items is the list of resource claims.</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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimlist-v1beta1-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/resourceclaims</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimlist-v1beta1-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/namespaces/{namespace}/resourceclaims</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/watch/resourceclaims</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-resourceclaim-v1beta1-resource-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1beta1/namespaces/{namespace}/resourceclaims/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1beta1-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="resourceclaim-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourceClaim</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>ResourceClaim</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="#resourceclaim-v1-core">v1</a>
<a href="#resourceclaim-v1beta1-resource-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="#resourceclaimlist-v1alpha3-resource-k8s-io">ResourceClaimList [resource/v1alpha3]</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/sig-architecture/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/sig-architecture/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="#resourceclaimspec-v1alpha3-resource-k8s-io">ResourceClaimSpec</a></I></TD><TD>Spec describes what is being requested and how to configure it. The spec is immutable.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#resourceclaimstatus-v1alpha3-resource-k8s-io">ResourceClaimStatus</a></I></TD><TD>Status describes whether the claim is ready to use and what has been allocated.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="resourceclaimspec-v1alpha3-resource-k8s-io">ResourceClaimSpec v1alpha3 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim [resource/v1alpha3]</a></LI>
<LI><a href="#resourceclaimtemplatespec-v1alpha3-resource-k8s-io">ResourceClaimTemplateSpec [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#deviceclaim-v1alpha3-resource-k8s-io">DeviceClaim</a></I></TD><TD>Devices defines how to request devices.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceclaimstatus-v1alpha3-resource-k8s-io">ResourceClaimStatus v1alpha3 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allocation</CODE><BR /><I><a href="#allocationresult-v1alpha3-resource-k8s-io">AllocationResult</a></I></TD><TD>Allocation is set once the claim has been allocated successfully.</TD></TR>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#allocateddevicestatus-v1alpha3-resource-k8s-io">AllocatedDeviceStatus</a> array</I></TD><TD>Devices contains the status of each device allocated for this claim, as reported by the driver. This can include driver-specific information. Entries are owned by their respective drivers.</TD></TR>
<TR><TD><CODE>reservedFor</CODE><BR /><I><a href="#resourceclaimconsumerreference-v1alpha3-resource-k8s-io">ResourceClaimConsumerReference</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>uid</I></TD><TD>ReservedFor indicates which entities are currently allowed to use the claim. A Pod which references a ResourceClaim which is not reserved for that Pod will not be started. A claim that is in use or might be in use because it has been reserved must not get deallocated. In a cluster with multiple scheduler instances, two pods might get scheduled concurrently by different schedulers. When they reference the same ResourceClaim which already has reached its maximum number of consumers, only one pod can be scheduled. Both schedulers try to add their pod to the claim.status.reservedFor field, but only the update that reaches the API server first gets stored. The other one fails with an error and the scheduler which issued it knows that it must put the pod back into the queue, waiting for the ResourceClaim to become usable again. There can be at most 32 such reservations. This may get increased in the future, but not reduced.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceclaimlist-v1alpha3-resource-k8s-io">ResourceClaimList v1alpha3 resource</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a> array</I></TD><TD>Items is the list of resource claims.</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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimlist-v1alpha3-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/resourceclaims</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimlist-v1alpha3-resource-k8s-io">ResourceClaimList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/namespaces/{namespace}/resourceclaims/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/namespaces/{namespace}/resourceclaims</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ResourceClaim. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/resourceclaims</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-resourceclaim-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified ResourceClaim</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaims/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaim-v1alpha3-resource-k8s-io">ResourceClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="resourceclaimconsumerreference-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourceClaimConsumerReference</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>ResourceClaimConsumerReference</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="#resourceclaimconsumerreference-v1beta1-resource-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="#resourceclaimstatus-v1alpha3-resource-k8s-io">ResourceClaimStatus [resource/v1alpha3]</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. It is empty for the core API. This matches the group in the APIVersion that is used when creating the resources.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of resource being referenced.</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>Resource is the type of resource being referenced, for example &#34;pods&#34;.</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID identifies exactly one incarnation of the resource.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourceClaimTemplate</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>ResourceClaimTemplate</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="#resourceclaimtemplate-v1beta1-resource-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="#resourceclaimtemplatelist-v1alpha3-resource-k8s-io">ResourceClaimTemplateList [resource/v1alpha3]</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/sig-architecture/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/sig-architecture/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="#resourceclaimtemplatespec-v1alpha3-resource-k8s-io">ResourceClaimTemplateSpec</a></I></TD><TD>Describes the ResourceClaim that is to be generated. This field is immutable. A ResourceClaim will get created by the control plane for a Pod when needed and then not get updated anymore.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="resourceclaimtemplatespec-v1alpha3-resource-k8s-io">ResourceClaimTemplateSpec v1alpha3 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate [resource/v1alpha3]</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>ObjectMeta may contain labels and annotations that will be copied into the ResourceClaim when creating it. No other fields are allowed and will be rejected during validation.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#resourceclaimspec-v1alpha3-resource-k8s-io">ResourceClaimSpec</a></I></TD><TD>Spec for the ResourceClaim. The entire content is copied unchanged into the ResourceClaim that gets created from this template. The same fields as in a ResourceClaim are also valid here.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceclaimtemplatelist-v1alpha3-resource-k8s-io">ResourceClaimTemplateList v1alpha3 resource</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a> array</I></TD><TD>Items is the list of resource claim 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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaimtemplates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaimtemplates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplate-v1alpha3-resource-k8s-io">ResourceClaimTemplate</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/namespaces/{namespace}/resourceclaimtemplates</CODE></P>
<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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplatelist-v1alpha3-resource-k8s-io">ResourceClaimTemplateList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-all-namespaces-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">List All Namespaces</H2>
<P>list or watch objects of kind ResourceClaimTemplate</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/resourceclaimtemplates</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceclaimtemplatelist-v1alpha3-resource-k8s-io">ResourceClaimTemplateList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/namespaces/{namespace}/resourceclaimtemplates/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceClaimTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/namespaces/{namespace}/resourceclaimtemplates</CODE></P>
<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>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-all-namespaces-resourceclaimtemplate-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ResourceClaimTemplate. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/resourceclaimtemplates</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="resourcepool-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourcePool</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>ResourcePool</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="#resourcepool-v1beta1-resource-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="#resourceslicespec-v1alpha3-resource-k8s-io">ResourceSliceSpec [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>generation</CODE><BR /><I>integer</I></TD><TD>Generation tracks the change in a pool over time. Whenever a driver changes something about one or more of the resources in a pool, it must change the generation in all ResourceSlices which are part of that pool. Consumers of ResourceSlices should only consider resources from the pool with the highest generation number. The generation may be reset by drivers, which should be fine for consumers, assuming that all ResourceSlices in a pool are updated to match or deleted. Combined with ResourceSliceCount, this mechanism enables consumers to detect pools which are comprised of multiple ResourceSlices and are in an incomplete state.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is used to identify the pool. For node-local devices, this is often the node name, but this is not required. It must not be longer than 253 characters and must consist of one or more DNS sub-domains separated by slashes. This field is immutable.</TD></TR>
<TR><TD><CODE>resourceSliceCount</CODE><BR /><I>integer</I></TD><TD>ResourceSliceCount is the total number of ResourceSlices in the pool at this generation number. Must be greater than zero. Consumers can use this to check whether they have seen all ResourceSlices belonging to the same pool.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="resourceslice-v1alpha3-resource-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ResourceSlice</span> <span class="v">v1alpha3</span> <span class="g">resource.k8s.io</span></span></H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>resource.k8s.io</CODE></TD><TD><CODE>v1alpha3</CODE></TD><TD><CODE>ResourceSlice</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="#resourceslice-v1beta1-resource-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="#resourceslicelist-v1alpha3-resource-k8s-io">ResourceSliceList [resource/v1alpha3]</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/sig-architecture/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/sig-architecture/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="#resourceslicespec-v1alpha3-resource-k8s-io">ResourceSliceSpec</a></I></TD><TD>Contains the information published by the driver. Changing the spec automatically increments the metadata.generation number.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="resourceslicespec-v1alpha3-resource-k8s-io">ResourceSliceSpec v1alpha3 resource</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice [resource/v1alpha3]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allNodes</CODE><BR /><I>boolean</I></TD><TD>AllNodes indicates that all nodes have access to the resources in the pool. Exactly one of NodeName, NodeSelector and AllNodes must be set.</TD></TR>
<TR><TD><CODE>devices</CODE><BR /><I><a href="#device-v1alpha3-resource-k8s-io">Device</a> array</I></TD><TD>Devices lists some or all of the devices in this pool. Must not have more than 128 entries.</TD></TR>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver identifies the DRA driver providing the capacity information. A field selector can be used to list only ResourceSlice objects with a certain driver name. Must be a DNS subdomain and should end with a DNS domain owned by the vendor of the driver. This field is immutable.</TD></TR>
<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>NodeName identifies the node which provides the resources in this pool. A field selector can be used to list only ResourceSlice objects belonging to a certain node. This field can be used to limit access from nodes to ResourceSlices with the same node name. It also indicates to autoscalers that adding new nodes of the same type as some old node might also make new resources available. Exactly one of NodeName, NodeSelector and AllNodes must be set. This field is immutable.</TD></TR>
<TR><TD><CODE>nodeSelector</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>NodeSelector defines which nodes have access to the resources in the pool, when that pool is not limited to a single node. Must use exactly one term. Exactly one of NodeName, NodeSelector and AllNodes must be set.</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I><a href="#resourcepool-v1alpha3-resource-k8s-io">ResourcePool</a></I></TD><TD>Pool describes the pool that this ResourceSlice belongs to.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="resourceslicelist-v1alpha3-resource-k8s-io">ResourceSliceList v1alpha3 resource</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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a> array</I></TD><TD>Items is the list of resource ResourceSlices.</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/sig-architecture/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>
</DIV>
<DIV class="operation-category-container" id="write-operations-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/resource.k8s.io/v1alpha3/resourceslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/resource.k8s.io/v1alpha3/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/resource.k8s.io/v1alpha3/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1alpha3/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/resource.k8s.io/v1alpha3/resourceslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceslice-v1alpha3-resource-k8s-io">ResourceSlice</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ResourceSlice</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/resourceslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourceslicelist-v1alpha3-resource-k8s-io">ResourceSliceList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ResourceSlice. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/resourceslices/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceSlice</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-resourceslice-v1alpha3-resource-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ResourceSlice. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/resource.k8s.io/v1alpha3/watch/resourceslices</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="selfsubjectreview-v1beta1-authentication-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">SelfSubjectReview</span> <span class="v">v1beta1</span> <span class="g">authentication.k8s.io</span></span></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>SelfSubjectReview</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="#selfsubjectreview-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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#selfsubjectreviewstatus-v1beta1-authentication-k8s-io">SelfSubjectReviewStatus</a></I></TD><TD>Status is filled in by the server with the user attributes.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="selfsubjectreviewstatus-v1beta1-authentication-k8s-io">SelfSubjectReviewStatus v1beta1 authentication</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview [authentication/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>userInfo</CODE><BR /><I><a href="#userinfo-v1-authentication-k8s-io">UserInfo</a></I></TD><TD>User attributes of the user making this request.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-selfsubjectreview-v1beta1-authentication-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-selfsubjectreview-v1beta1-authentication-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a SelfSubjectReview</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/authentication.k8s.io/v1beta1/selfsubjectreviews</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#selfsubjectreview-v1beta1-authentication-k8s-io">SelfSubjectReview</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="servicereference-v1-apiextensions-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ServiceReference</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>ServiceReference</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="#webhookclientconfig-v1-apiextensions-k8s-io">WebhookClientConfig [apiextensions/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. 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 at which the webhook will be contacted.</TD></TR>
<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>port is an optional service port at which the webhook will be contacted. `port` should be a valid port number (1-65535, inclusive). Defaults to 443 for backward compatibility.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="servicereference-v1-apiregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ServiceReference</span> <span class="v">v1</span> <span class="g">apiregistration.k8s.io</span></span></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>ServiceReference</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="#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>
<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>If specified, the port on the service that hosting webhook. Default to 443 for backward compatibility. `port` should be a valid port number (1-65535, inclusive).</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="subject-v1-rbac-authorization-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Subject</span> <span class="v">v1</span> <span class="g">rbac.authorization.k8s.io</span></span></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>Subject</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="#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>
</DIV>
<DIV class="resource-container" id="tokenrequest-v1-storage-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">TokenRequest</span> <span class="v">v1</span> <span class="g">storage.k8s.io</span></span></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>TokenRequest</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="#csidriverspec-v1-storage-k8s-io">CSIDriverSpec [storage/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 in &#34;TokenRequestSpec&#34;. It will default to the audiences of kube apiserver.</TD></TR>
<TR><TD><CODE>expirationSeconds</CODE><BR /><I>integer</I></TD><TD>expirationSeconds is the duration of validity of the token in &#34;TokenRequestSpec&#34;. It has the same default value of &#34;ExpirationSeconds&#34; in &#34;TokenRequestSpec&#34;.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="typechecking-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">TypeChecking</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>TypeChecking</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="#typechecking-v1-admissionregistration-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="#validatingadmissionpolicystatus-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expressionWarnings</CODE><BR /><I><a href="#expressionwarning-v1beta1-admissionregistration-k8s-io">ExpressionWarning</a> array</I></TD><TD>The type checking warnings for each expression.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ValidatingAdmissionPolicy</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>ValidatingAdmissionPolicy</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="#validatingadmissionpolicy-v1-admissionregistration-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="#validatingadmissionpolicylist-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList [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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#validatingadmissionpolicyspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec</a></I></TD><TD>Specification of the desired behavior of the ValidatingAdmissionPolicy.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#validatingadmissionpolicystatus-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus</a></I></TD><TD>The status of the ValidatingAdmissionPolicy, including warnings that are useful to determine if the policy behaves in the expected way. Populated by the system. Read-only.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="validatingadmissionpolicyspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec v1beta1 admissionregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>auditAnnotations</CODE><BR /><I><a href="#auditannotation-v1beta1-admissionregistration-k8s-io">AuditAnnotation</a> array</I></TD><TD>auditAnnotations contains CEL expressions which are used to produce audit annotations for the audit event of the API request. validations and auditAnnotations may not both be empty; a least one of validations or auditAnnotations is required.</TD></TR>
<TR><TD><CODE>failurePolicy</CODE><BR /><I>string</I></TD><TD>failurePolicy defines how to handle failures for the admission policy. Failures can occur from CEL expression parse errors, type check errors, runtime errors and invalid or mis-configured policy definitions or bindings. A policy is invalid if spec.paramKind refers to a non-existent Kind. A binding is invalid if spec.paramRef.name refers to a non-existent resource. failurePolicy does not define how validations that evaluate to false are handled. When failurePolicy is set to Fail, ValidatingAdmissionPolicyBinding validationActions define how failures are enforced. Allowed values are Ignore or Fail. Defaults to Fail.</TD></TR>
<TR><TD><CODE>matchConditions</CODE><BR /><I><a href="#matchcondition-v1beta1-admissionregistration-k8s-io">MatchCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>MatchConditions is a list of conditions that must be met for a request to be validated. Match conditions filter requests that have already been matched by the rules, namespaceSelector, and objectSelector. An empty list of matchConditions matches all requests. There are a maximum of 64 match conditions allowed. If a parameter object is provided, it can be accessed via the `params` handle in the same manner as validation expressions. The exact matching logic is (in order): 1. If ANY matchCondition evaluates to FALSE, the policy is skipped. 2. If ALL matchConditions evaluate to TRUE, the policy is evaluated. 3. If any matchCondition evaluates to an error (but none are FALSE): - If failurePolicy=Fail, reject the request - If failurePolicy=Ignore, the policy is skipped</TD></TR>
<TR><TD><CODE>matchConstraints</CODE><BR /><I><a href="#matchresources-v1beta1-admissionregistration-k8s-io">MatchResources</a></I></TD><TD>MatchConstraints specifies what resources this policy is designed to validate. The AdmissionPolicy cares about a request if it matches _all_ Constraints. However, in order to prevent clusters from being put into an unstable state that cannot be recovered from via the API ValidatingAdmissionPolicy cannot match ValidatingAdmissionPolicy and ValidatingAdmissionPolicyBinding. Required.</TD></TR>
<TR><TD><CODE>paramKind</CODE><BR /><I><a href="#paramkind-v1beta1-admissionregistration-k8s-io">ParamKind</a></I></TD><TD>ParamKind specifies the kind of resources used to parameterize this policy. If absent, there are no parameters for this policy and the param CEL variable will not be provided to validation expressions. If ParamKind refers to a non-existent kind, this policy definition is mis-configured and the FailurePolicy is applied. If paramKind is specified but paramRef is unset in ValidatingAdmissionPolicyBinding, the params variable will be null.</TD></TR>
<TR><TD><CODE>validations</CODE><BR /><I><a href="#validation-v1beta1-admissionregistration-k8s-io">Validation</a> array</I></TD><TD>Validations contain CEL expressions which is used to apply the validation. Validations and AuditAnnotations may not both be empty; a minimum of one Validations or AuditAnnotations is required.</TD></TR>
<TR><TD><CODE>variables</CODE><BR /><I><a href="#variable-v1beta1-admissionregistration-k8s-io">Variable</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Variables contain definitions of variables that can be used in composition of other expressions. Each variable is defined as a named CEL expression. The variables defined here will be available under `variables` in other expressions of the policy except MatchConditions because MatchConditions are evaluated before the rest of the policy. The expression of a variable can refer to other variables defined earlier in the list but not those after. Thus, Variables must be sorted by the order of first appearance and acyclic.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="validatingadmissionpolicystatus-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyStatus v1beta1 admissionregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy [admissionregistration/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="#condition-v1-meta">Condition</a> array</I></TD><TD>The conditions represent the latest available observations of a policy&#39;s current state.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The generation observed by the controller.</TD></TR>
<TR><TD><CODE>typeChecking</CODE><BR /><I><a href="#typechecking-v1beta1-admissionregistration-k8s-io">TypeChecking</a></I></TD><TD>The results of type checking for each expression. Presence of this field indicates the completion of the type checking.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="validatingadmissionpolicylist-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a> array</I></TD><TD>List of ValidatingAdmissionPolicy.</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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicylist-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ValidatingAdmissionPolicy. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1beta1/watch/validatingadmissionpolicies/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ValidatingAdmissionPolicy. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1beta1/watch/validatingadmissionpolicies</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="status-operations-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Status Operations</H2>
<DIV class="operation-container" id="patch-status-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch Status</H2>
<P>partially update status of the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="read-status-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read Status</H2>
<P>read status of the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-status-validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace Status</H2>
<P>replace status of the specified ValidatingAdmissionPolicy</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}/status</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicy-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">ValidatingAdmissionPolicyBinding</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>ValidatingAdmissionPolicyBinding</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="#validatingadmissionpolicybinding-v1-admissionregistration-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="#validatingadmissionpolicybindinglist-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList [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/sig-architecture/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/sig-architecture/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/sig-architecture/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#validatingadmissionpolicybindingspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec</a></I></TD><TD>Specification of the desired behavior of the ValidatingAdmissionPolicyBinding.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="validatingadmissionpolicybindingspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingSpec v1beta1 admissionregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>matchResources</CODE><BR /><I><a href="#matchresources-v1beta1-admissionregistration-k8s-io">MatchResources</a></I></TD><TD>MatchResources declares what resources match this binding and will be validated by it. Note that this is intersected with the policy&#39;s matchConstraints, so only requests that are matched by the policy can be selected by this. If this is unset, all resources matched by the policy are validated by this binding When resourceRules is unset, it does not constrain resource matching. If a resource is matched by the other fields of this object, it will be validated. Note that this is differs from ValidatingAdmissionPolicy matchConstraints, where resourceRules are required.</TD></TR>
<TR><TD><CODE>paramRef</CODE><BR /><I><a href="#paramref-v1beta1-admissionregistration-k8s-io">ParamRef</a></I></TD><TD>paramRef specifies the parameter resource used to configure the admission control policy. It should point to a resource of the type specified in ParamKind of the bound ValidatingAdmissionPolicy. If the policy specifies a ParamKind and the resource referred to by ParamRef does not exist, this binding is considered mis-configured and the FailurePolicy of the ValidatingAdmissionPolicy applied. If the policy does not specify a ParamKind then this field is ignored, and the rules are evaluated without a param.</TD></TR>
<TR><TD><CODE>policyName</CODE><BR /><I>string</I></TD><TD>PolicyName references a ValidatingAdmissionPolicy name which the ValidatingAdmissionPolicyBinding binds to. If the referenced resource does not exist, this binding is considered invalid and will be ignored Required.</TD></TR>
<TR><TD><CODE>validationActions</CODE><BR /><I>string array</I></TD><TD>validationActions declares how Validations of the referenced ValidatingAdmissionPolicy are enforced. If a validation evaluates to false it is always enforced according to these actions. Failures defined by the ValidatingAdmissionPolicy&#39;s FailurePolicy are enforced according to these actions only if the FailurePolicy is set to Fail, otherwise the failures are ignored. This includes compilation errors, runtime errors and misconfigurations of the policy. validationActions is declared as a set of action values. Order does not matter. validationActions may not contain duplicates of the same action. The supported actions values are: &#34;Deny&#34; specifies that a validation failure results in a denied request. &#34;Warn&#34; specifies that a validation failure is reported to the request client in HTTP Warning headers, with a warning code of 299. Warnings can be sent both for allowed or denied admission responses. &#34;Audit&#34; specifies that a validation failure is included in the published audit event for the request. The audit event will contain a `validation.policy.admission.k8s.io/validation_failure` audit annotation with a value containing the details of the validation failures, formatted as a JSON list of objects, each with the following fields: - message: The validation failure message string - policy: The resource name of the ValidatingAdmissionPolicy - binding: The resource name of the ValidatingAdmissionPolicyBinding - expressionIndex: The index of the failed validations in the ValidatingAdmissionPolicy - validationActions: The enforcement actions enacted for the validation failure Example audit annotation: `&#34;validation.policy.admission.k8s.io/validation_failure&#34;: &#34;[{\&#34;message\&#34;: \&#34;Invalid value\&#34;, {\&#34;policy\&#34;: \&#34;policy.example.com\&#34;, {\&#34;binding\&#34;: \&#34;policybinding.example.com\&#34;, {\&#34;expressionIndex\&#34;: \&#34;1\&#34;, {\&#34;validationActions\&#34;: [\&#34;Audit\&#34;]}]&#34;` Clients should expect to handle additional values by ignoring any values not recognized. &#34;Deny&#34; and &#34;Warn&#34; may not be used together since this combination needlessly duplicates the validation failure both in the API response body and the HTTP warning headers. Required.</TD></TR>
</TBODY>
</TABLE>
<H3 class="inline-definition" id="validatingadmissionpolicybindinglist-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a> array</I></TD><TD>List of PolicyBinding.</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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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>
<TR><TD>202<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind ValidatingAdmissionPolicyBinding</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingadmissionpolicybindinglist-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicyBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind ValidatingAdmissionPolicyBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1beta1/watch/validatingadmissionpolicybindings/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingAdmissionPolicyBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-validatingadmissionpolicybinding-v1beta1-admissionregistration-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of ValidatingAdmissionPolicyBinding. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/admissionregistration.k8s.io/v1beta1/watch/validatingadmissionpolicybindings</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="validation-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Validation</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>Validation</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="#validation-v1-admissionregistration-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="#validatingadmissionpolicyspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression represents the expression which will be evaluated by CEL. ref: https://github.com/google/cel-spec CEL expressions have access to the contents of the API request/response, organized into CEL variables as well as some other useful variables: - &#39;object&#39; - The object from the incoming request. The value is null for DELETE requests. - &#39;oldObject&#39; - The existing object. The value is null for CREATE requests. - &#39;request&#39; - Attributes of the API request([ref](/pkg/apis/admission/types.go#AdmissionRequest)). - &#39;params&#39; - Parameter resource referred to by the policy binding being evaluated. Only populated if the policy has a ParamKind. - &#39;namespaceObject&#39; - The namespace object that the incoming object belongs to. The value is null for cluster-scoped resources. - &#39;variables&#39; - Map of composited variables, from its name to its lazily evaluated value. For example, a variable named &#39;foo&#39; can be accessed as &#39;variables.foo&#39;. - &#39;authorizer&#39; - A CEL Authorizer. May be used to perform authorization checks for the principal (user or service account) of the request. See https://pkg.go.dev/k8s.io/apiserver/pkg/cel/library#Authz - &#39;authorizer.requestResource&#39; - A CEL ResourceCheck constructed from the &#39;authorizer&#39; and configured with the request resource. The `apiVersion`, `kind`, `metadata.name` and `metadata.generateName` are always accessible from the root of the object. No other metadata properties are accessible. Only property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible. Accessible property names are escaped according to the following rules when accessed in the expression: - &#39;__&#39; escapes to &#39;__underscores__&#39; - &#39;.&#39; escapes to &#39;__dot__&#39; - &#39;-&#39; escapes to &#39;__dash__&#39; - &#39;/&#39; escapes to &#39;__slash__&#39; - Property names that exactly match a CEL RESERVED keyword escape to &#39;__{keyword}__&#39;. The keywords are: &#34;true&#34;, &#34;false&#34;, &#34;null&#34;, &#34;in&#34;, &#34;as&#34;, &#34;break&#34;, &#34;const&#34;, &#34;continue&#34;, &#34;else&#34;, &#34;for&#34;, &#34;function&#34;, &#34;if&#34;, &#34;import&#34;, &#34;let&#34;, &#34;loop&#34;, &#34;package&#34;, &#34;namespace&#34;, &#34;return&#34;. Examples: - Expression accessing a property named &#34;namespace&#34;: {&#34;Expression&#34;: &#34;object.__namespace__ &gt; 0&#34;} - Expression accessing a property named &#34;x-prop&#34;: {&#34;Expression&#34;: &#34;object.x__dash__prop &gt; 0&#34;} - Expression accessing a property named &#34;redact__d&#34;: {&#34;Expression&#34;: &#34;object.redact__underscores__d &gt; 0&#34;} Equality on arrays with list type of &#39;set&#39; or &#39;map&#39; ignores element order, i.e. [1, 2] == [2, 1]. Concatenation on arrays with x-kubernetes-list-type use the semantics of the list type: - &#39;set&#39;: `X + Y` performs a union where the array positions of all elements in `X` are preserved and non-intersecting elements in `Y` are appended, retaining their partial order. - &#39;map&#39;: `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the values are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` with non-intersecting keys are appended, retaining their partial order. Required.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message represents the message displayed when validation fails. The message is required if the Expression contains line breaks. The message must not contain line breaks. If unset, the message is &#34;failed rule: {Rule}&#34;. e.g. &#34;must be a URL with the host matching spec.host&#34; If the Expression contains line breaks. Message is required. The message must not contain line breaks. If unset, the message is &#34;failed Expression: {Expression}&#34;.</TD></TR>
<TR><TD><CODE>messageExpression</CODE><BR /><I>string</I></TD><TD>messageExpression declares a CEL expression that evaluates to the validation failure message that is returned when this rule fails. Since messageExpression is used as a failure message, it must evaluate to a string. If both message and messageExpression are present on a validation, then messageExpression will be used if validation fails. If messageExpression results in a runtime error, the runtime error is logged, and the validation failure message is produced as if the messageExpression field were unset. If messageExpression evaluates to an empty string, a string with only spaces, or a string that contains line breaks, then the validation failure message will also be produced as if the messageExpression field were unset, and the fact that messageExpression produced an empty string/string with only spaces/string with line breaks will be logged. messageExpression has access to all the same variables as the `expression` except for &#39;authorizer&#39; and &#39;authorizer.requestResource&#39;. Example: &#34;object.x must be less than max (&#34;+string(params.max)+&#34;)&#34;</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Reason represents a machine-readable description of why this validation failed. If this is the first validation in the list to fail, this reason, as well as the corresponding HTTP response code, are used in the HTTP response to the client. The currently supported reasons are: &#34;Unauthorized&#34;, &#34;Forbidden&#34;, &#34;Invalid&#34;, &#34;RequestEntityTooLarge&#34;. If not set, StatusReasonInvalid is used in the response to the client.</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="variable-v1beta1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Variable</span> <span class="v">v1beta1</span> <span class="g">admissionregistration.k8s.io</span></span></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>Variable</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="#variable-v1-admissionregistration-k8s-io">v1</a>
<a href="#variable-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="#validatingadmissionpolicyspec-v1beta1-admissionregistration-k8s-io">ValidatingAdmissionPolicySpec [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression is the expression that will be evaluated as the value of the variable. The CEL expression has access to the same identifiers as the CEL expressions in Validation.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the variable. The name must be a valid CEL identifier and unique among all variables. The variable can be accessed in other expressions through `variables` For example, if name is &#34;foo&#34;, the variable will be available as `variables.foo`</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="variable-v1alpha1-admissionregistration-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">Variable</span> <span class="v">v1alpha1</span> <span class="g">admissionregistration.k8s.io</span></span></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>Variable</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="#variable-v1-admissionregistration-k8s-io">v1</a>
<a href="#variable-v1beta1-admissionregistration-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="#mutatingadmissionpolicyspec-v1alpha1-admissionregistration-k8s-io">MutatingAdmissionPolicySpec [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>expression</CODE><BR /><I>string</I></TD><TD>Expression is the expression that will be evaluated as the value of the variable. The CEL expression has access to the same identifiers as the CEL expressions in Validation.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the variable. The name must be a valid CEL identifier and unique among all variables. The variable can be accessed in other expressions through `variables` For example, if name is &#34;foo&#34;, the variable will be available as `variables.foo`</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="resource-container" id="volumeattributesclass-v1alpha1-storage-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">VolumeAttributesClass</span> <span class="v">v1alpha1</span> <span class="g">storage.k8s.io</span></span></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>VolumeAttributesClass</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="#volumeattributesclass-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="#volumeattributesclasslist-v1alpha1-storage-k8s-io">VolumeAttributesClassList [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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>driverName</CODE><BR /><I>string</I></TD><TD>Name of the CSI driver This field is immutable.</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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>parameters</CODE><BR /><I>object</I></TD><TD>parameters hold volume attributes defined by the CSI driver. These values are opaque to the Kubernetes and are passed directly to the CSI driver. The underlying storage provider supports changing these attributes on an existing volume, however the parameters field itself is immutable. To invoke a volume update, a new VolumeAttributesClass should be created with new parameters, and the PersistentVolumeClaim should be updated to reference the new VolumeAttributesClass. This field is required and must contain at least one key/value pair. The keys cannot be empty, and the maximum number of parameters is 512, with a cumulative max size of 256K. If the CSI driver rejects invalid parameters, the target PersistentVolumeClaim will be set to an &#34;Infeasible&#34; state in the modifyVolumeStatus field.</TD></TR>
</TBODY>
</TABLE>
<DIV class="inline-definitions-container">
<H3 class="inline-definition" id="volumeattributesclasslist-v1alpha1-storage-k8s-io">VolumeAttributesClassList 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/sig-architecture/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a> array</I></TD><TD>items is the list of VolumeAttributesClass 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/sig-architecture/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/sig-architecture/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-category-container" id="write-operations-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation-category">Write Operations</H2>
<DIV class="operation-container" id="create-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation">Create</H2>
<P>create a VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>POST /apis/storage.k8s.io/v1alpha1/volumeattributesclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="patch-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation">Patch</H2>
<P>partially update the specified VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>PATCH /apis/storage.k8s.io/v1alpha1/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
<TR><TD><CODE>force</CODE></TD><TD>Force is going to "force" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.</TD></TR>
</TBODY>
</TABLE>
<H3>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="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="replace-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation">Replace</H2>
<P>replace the specified VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>PUT /apis/storage.k8s.io/v1alpha1/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldManager</CODE></TD><TD>fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.</TD></TR>
<TR><TD><CODE>fieldValidation</CODE></TD><TD>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation">Delete</H2>
<P>delete a VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1alpha1/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</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="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>202<br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="delete-collection-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation">Delete Collection</H2>
<P>delete collection of VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>DELETE /apis/storage.k8s.io/v1alpha1/volumeattributesclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>dryRun</CODE></TD><TD>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</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>ignoreStoreReadErrorWithClusterBreakingPotential</CODE></TD><TD>if set to true, it will trigger an unsafe deletion of the resource in case the normal deletion flow fails with a corrupt object error. A resource is considered corrupt if it can not be retrieved from the underlying storage successfully because of a) its data can not be transformed e.g. decryption failure, or b) it fails to decode into an object. NOTE: unsafe deletion ignores finalizer constraints, skips precondition checks, and removes the object from the storage. WARNING: This may potentially break the cluster if the workload associated with the resource being unsafe-deleted relies on normal deletion flow. Use only if you REALLY know what you are doing. The default value is false, and the user must opt in to enable it</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</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>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
</TBODY>
</TABLE>
<H3>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>
</DIV>
</DIV>
<DIV class="operation-category-container" id="read-operations-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation-category">Read Operations</H2>
<DIV class="operation-container" id="read-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation">Read</H2>
<P>read the specified VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1alpha1/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattributesclass-v1alpha1-storage-k8s-io">VolumeAttributesClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="list-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation">List</H2>
<P>list or watch objects of kind VolumeAttributesClass</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1alpha1/volumeattributesclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattributesclasslist-v1alpha1-storage-k8s-io">VolumeAttributesClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
</DIV>
<DIV class="operation-container" id="watch-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation">Watch</H2>
<P>watch changes to an object of kind VolumeAttributesClass. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1alpha1/watch/volumeattributesclasses/{name}</CODE></P>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttributesClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
<DIV class="operation-container" id="watch-list-volumeattributesclass-v1alpha1-storage-k8s-io">
<H2 class="toc-item operation">Watch List</H2>
<P>watch individual changes to a list of VolumeAttributesClass. deprecated: use the 'watch' parameter with a list operation instead.</P>
<H3>HTTP Request</H3>
<p><CODE>GET /apis/storage.k8s.io/v1alpha1/watch/volumeattributesclasses</CODE></P>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowWatchBookmarks</CODE></TD><TD>allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.</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 together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list 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. Defaults to 'false' unless the user-agent indicates a browser or command-line HTTP tool (curl and wget).</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>resourceVersionMatch</CODE></TD><TD>resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset</TD></TR>
<TR><TD><CODE>sendInitialEvents</CODE></TD><TD>`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"k8s.io/initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</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>
</DIV>
</DIV>
</DIV>
<DIV class="resource-container" id="webhookclientconfig-v1-apiextensions-k8s-io">
<H1 class="toc-item resource"><span class="gvk"><span class="k">WebhookClientConfig</span> <span class="v">v1</span> <span class="g">apiextensions.k8s.io</span></span></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>v1</CODE></TD><TD><CODE>WebhookClientConfig</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="#webhookconversion-v1-apiextensions-k8s-io">WebhookConversion [apiextensions/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 the webhook&#39;s server certificate. If unspecified, system trust roots on the apiserver are used.</TD></TR>
<TR><TD><CODE>service</CODE><BR /><I><a href="#servicereference-v1-apiextensions-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`.</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>
</DIV>
</DIV>
</DIV>
</DIV>
<SCRIPT src="/js/jquery-3.6.0.min.js"></SCRIPT>
<SCRIPT src="/js/jquery.scrollTo-2.1.3.min.js"></SCRIPT>
<SCRIPT src="/js/bootstrap-5.3.2.min.js"></SCRIPT>
<SCRIPT src="/js/apiref.js"></SCRIPT>
</BODY>
</HTML>