"description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
"name":"continue",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.",
"name":"fieldSelector",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.",
"name":"labelSelector",
"in":"query"
},
{
"uniqueItems":true,
"type":"integer",
"description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
"name":"limit",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.",
"name":"resourceVersion",
"in":"query"
},
{
"uniqueItems":true,
"type":"integer",
"description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
"name":"timeoutSeconds",
"in":"query"
},
{
"uniqueItems":true,
"type":"boolean",
"description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
"description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
"name":"continue",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.",
"name":"fieldSelector",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.",
"name":"labelSelector",
"in":"query"
},
{
"uniqueItems":true,
"type":"integer",
"description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
"name":"limit",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.",
"name":"resourceVersion",
"in":"query"
},
{
"uniqueItems":true,
"type":"integer",
"description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
"name":"timeoutSeconds",
"in":"query"
},
{
"uniqueItems":true,
"type":"boolean",
"description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
"name":"dryRun",
"in":"query"
},
{
"uniqueItems":true,
"type":"integer",
"description":"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.",
"name":"gracePeriodSeconds",
"in":"query"
},
{
"uniqueItems":true,
"type":"boolean",
"description":"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.",
"name":"orphanDependents",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"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.",
"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
"description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
"name":"continue",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.",
"name":"fieldSelector",
"in":"query"
},
{
"uniqueItems":true,
"type":"boolean",
"description":"If true, partially initialized resources are included in the response.",
"name":"includeUninitialized",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.",
"name":"labelSelector",
"in":"query"
},
{
"uniqueItems":true,
"type":"integer",
"description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
"name":"limit",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"If 'true', then the output is pretty printed.",
"name":"pretty",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.",
"name":"resourceVersion",
"in":"query"
},
{
"uniqueItems":true,
"type":"integer",
"description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
"name":"timeoutSeconds",
"in":"query"
},
{
"uniqueItems":true,
"type":"boolean",
"description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
"description":"watch changes to an object of kind AuditSink. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.",
"description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
"name":"continue",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.",
"name":"fieldSelector",
"in":"query"
},
{
"uniqueItems":true,
"type":"boolean",
"description":"If true, partially initialized resources are included in the response.",
"name":"includeUninitialized",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.",
"name":"labelSelector",
"in":"query"
},
{
"uniqueItems":true,
"type":"integer",
"description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
"name":"limit",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"name of the AuditSink",
"name":"name",
"in":"path",
"required":true
},
{
"uniqueItems":true,
"type":"string",
"description":"If 'true', then the output is pretty printed.",
"name":"pretty",
"in":"query"
},
{
"uniqueItems":true,
"type":"string",
"description":"When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.",
"name":"resourceVersion",
"in":"query"
},
{
"uniqueItems":true,
"type":"integer",
"description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
"name":"timeoutSeconds",
"in":"query"
},
{
"uniqueItems":true,
"type":"boolean",
"description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
"description":"AuditSink represents a cluster level audit sink",
"properties":{
"apiVersion":{
"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources",
"type":"string"
},
"kind":{
"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds",
"description":"AuditSinkList is a list of AuditSink items.",
"required":[
"items"
],
"properties":{
"apiVersion":{
"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources",
"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds",
"description":"WebhookClientConfig contains the information to make a connection with the webhook",
"properties":{
"caBundle":{
"description":"`caBundle` is a PEM encoded CA bundle which will be used to validate the webhook's server certificate. defaults to the apiservers CA bundle for the endpoint type",
"type":"string",
"format":"byte"
},
"service":{
"description":"`service` is a reference to the service for this webhook. Either `service` or `url` must be specified.\n\nIf the webhook is running within the cluster, then you should use `service`.\n\nPort 443 will be used if it is open, otherwise it is an error.",
"description":"`url` gives the location of the webhook, in standard URL form (`[scheme://]host:port/path`). Exactly one of `url` or `service` must be specified.\n\nThe `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.\n\nPlease 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.\n\nThe scheme must be \"https\"; the URL must begin with \"https://\".\n\nA 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.\n\nAttempting to use a user or basic auth e.g. \"user:password@\" is not allowed. Fragments (\"#...\") and query parameters (\"?...\") are not allowed, either.",
"description":"WebhookThrottleConfig holds the configuration for throttling events",
"properties":{
"burst":{
"description":"ThrottleBurst is the maximum number of events sent at the same moment default 15 QPS",
"type":"integer",
"format":"int64"
},
"qps":{
"description":"ThrottleQPS maximum number of batches per second default 10 QPS",
"type":"integer",
"format":"int64"
}
}
},
"io.k8s.api.authentication.v1.TokenReview":{
"description":"TokenReview attempts to authenticate a token to a known user. Note: TokenReview requests may be cached by the webhook token authenticator plugin in the kube-apiserver.",
"description":"APIGroup contains the name, the supported versions, and the preferred version of a group.",
"required":[
"name",
"versions"
],
"properties":{
"kind":{
"type":"string",
"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds"
},
"apiVersion":{
"type":"string",
"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources"
},
"name":{
"type":"string",
"description":"name is the name of the group."
},
"versions":{
"type":"array",
"items":{
"$ref":"v1.GroupVersionForDiscovery"
},
"description":"versions are the versions supported in this group."
},
"preferredVersion":{
"$ref":"v1.GroupVersionForDiscovery",
"description":"preferredVersion is the version preferred by the API server, which probably is the storage version."
},
"serverAddressByClientCIDRs":{
"type":"array",
"items":{
"$ref":"v1.ServerAddressByClientCIDR"
},
"description":"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."
}
}
},
"v1.GroupVersionForDiscovery":{
"id":"v1.GroupVersionForDiscovery",
"description":"GroupVersion contains the \"group/version\" and \"version\" string of a version. It is made a struct to keep extensibility.",
"required":[
"groupVersion",
"version"
],
"properties":{
"groupVersion":{
"type":"string",
"description":"groupVersion specifies the API group and version in the form \"group/version\""
},
"version":{
"type":"string",
"description":"version specifies the version in the form of \"version\". This is to save the clients the trouble of splitting the GroupVersion."
}
}
},
"v1.ServerAddressByClientCIDR":{
"id":"v1.ServerAddressByClientCIDR",
"description":"ServerAddressByClientCIDR helps the client to determine the server address that they should use, depending on the clientCIDR that they match.",
"required":[
"clientCIDR",
"serverAddress"
],
"properties":{
"clientCIDR":{
"type":"string",
"description":"The CIDR with which clients can match their IP to figure out the server address that they should use."
},
"serverAddress":{
"type":"string",
"description":"Address of this server, suitable for a client that matches the above CIDR. This can be a hostname, hostname:port, IP or IP:port."
"description":"API at /apis/auditregistration.k8s.io/v1alpha1",
"operations":[
{
"type":"v1alpha1.AuditSinkList",
"method":"GET",
"summary":"list or watch objects of kind AuditSink",
"nickname":"listAuditSink",
"parameters":[
{
"type":"string",
"paramType":"query",
"name":"pretty",
"description":"If 'true', then the output is pretty printed.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"labelSelector",
"description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"fieldSelector",
"description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"includeUninitialized",
"description":"If true, partially initialized resources are included in the response.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"watch",
"description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"resourceVersion",
"description":"When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.",
"required":false,
"allowMultiple":false
},
{
"type":"integer",
"paramType":"query",
"name":"timeoutSeconds",
"description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
"required":false,
"allowMultiple":false
},
{
"type":"integer",
"paramType":"query",
"name":"limit",
"description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"continue",
"description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
"description":"If 'true', then the output is pretty printed.",
"required":false,
"allowMultiple":false
},
{
"type":"v1alpha1.AuditSink",
"paramType":"body",
"name":"body",
"description":"",
"required":true,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"dryRun",
"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"includeUninitialized",
"description":"If IncludeUninitialized is specified, the object may be returned without completing initialization.",
"required":false,
"allowMultiple":false
}
],
"responseMessages":[
{
"code":200,
"message":"OK",
"responseModel":"v1alpha1.AuditSink"
},
{
"code":201,
"message":"Created",
"responseModel":"v1alpha1.AuditSink"
},
{
"code":202,
"message":"Accepted",
"responseModel":"v1alpha1.AuditSink"
}
],
"produces":[
"application/json",
"application/yaml",
"application/vnd.kubernetes.protobuf"
],
"consumes":[
"*/*"
]
},
{
"type":"v1.Status",
"method":"DELETE",
"summary":"delete collection of AuditSink",
"nickname":"deletecollectionAuditSink",
"parameters":[
{
"type":"string",
"paramType":"query",
"name":"pretty",
"description":"If 'true', then the output is pretty printed.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"labelSelector",
"description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"fieldSelector",
"description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"includeUninitialized",
"description":"If true, partially initialized resources are included in the response.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"watch",
"description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"resourceVersion",
"description":"When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.",
"required":false,
"allowMultiple":false
},
{
"type":"integer",
"paramType":"query",
"name":"timeoutSeconds",
"description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
"required":false,
"allowMultiple":false
},
{
"type":"integer",
"paramType":"query",
"name":"limit",
"description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"continue",
"description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
"description":"API at /apis/auditregistration.k8s.io/v1alpha1",
"operations":[
{
"type":"v1.WatchEvent",
"method":"GET",
"summary":"watch individual changes to a list of AuditSink. deprecated: use the 'watch' parameter with a list operation instead.",
"nickname":"watchAuditSinkList",
"parameters":[
{
"type":"string",
"paramType":"query",
"name":"pretty",
"description":"If 'true', then the output is pretty printed.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"labelSelector",
"description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"fieldSelector",
"description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"includeUninitialized",
"description":"If true, partially initialized resources are included in the response.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"watch",
"description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"resourceVersion",
"description":"When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.",
"required":false,
"allowMultiple":false
},
{
"type":"integer",
"paramType":"query",
"name":"timeoutSeconds",
"description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
"required":false,
"allowMultiple":false
},
{
"type":"integer",
"paramType":"query",
"name":"limit",
"description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"continue",
"description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
"description":"API at /apis/auditregistration.k8s.io/v1alpha1",
"operations":[
{
"type":"v1alpha1.AuditSink",
"method":"GET",
"summary":"read the specified AuditSink",
"nickname":"readAuditSink",
"parameters":[
{
"type":"string",
"paramType":"query",
"name":"pretty",
"description":"If 'true', then the output is pretty printed.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"export",
"description":"Should this value be exported. Export strips fields that a user can not specify.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"exact",
"description":"Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"path",
"name":"name",
"description":"name of the AuditSink",
"required":true,
"allowMultiple":false
}
],
"responseMessages":[
{
"code":200,
"message":"OK",
"responseModel":"v1alpha1.AuditSink"
}
],
"produces":[
"application/json",
"application/yaml",
"application/vnd.kubernetes.protobuf"
],
"consumes":[
"*/*"
]
},
{
"type":"v1alpha1.AuditSink",
"method":"PUT",
"summary":"replace the specified AuditSink",
"nickname":"replaceAuditSink",
"parameters":[
{
"type":"string",
"paramType":"query",
"name":"pretty",
"description":"If 'true', then the output is pretty printed.",
"required":false,
"allowMultiple":false
},
{
"type":"v1alpha1.AuditSink",
"paramType":"body",
"name":"body",
"description":"",
"required":true,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"dryRun",
"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"path",
"name":"name",
"description":"name of the AuditSink",
"required":true,
"allowMultiple":false
}
],
"responseMessages":[
{
"code":200,
"message":"OK",
"responseModel":"v1alpha1.AuditSink"
},
{
"code":201,
"message":"Created",
"responseModel":"v1alpha1.AuditSink"
}
],
"produces":[
"application/json",
"application/yaml",
"application/vnd.kubernetes.protobuf"
],
"consumes":[
"*/*"
]
},
{
"type":"v1alpha1.AuditSink",
"method":"PATCH",
"summary":"partially update the specified AuditSink",
"nickname":"patchAuditSink",
"parameters":[
{
"type":"string",
"paramType":"query",
"name":"pretty",
"description":"If 'true', then the output is pretty printed.",
"required":false,
"allowMultiple":false
},
{
"type":"v1.Patch",
"paramType":"body",
"name":"body",
"description":"",
"required":true,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"dryRun",
"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"path",
"name":"name",
"description":"name of the AuditSink",
"required":true,
"allowMultiple":false
}
],
"responseMessages":[
{
"code":200,
"message":"OK",
"responseModel":"v1alpha1.AuditSink"
}
],
"produces":[
"application/json",
"application/yaml",
"application/vnd.kubernetes.protobuf"
],
"consumes":[
"application/json-patch+json",
"application/merge-patch+json",
"application/strategic-merge-patch+json"
]
},
{
"type":"v1.Status",
"method":"DELETE",
"summary":"delete an AuditSink",
"nickname":"deleteAuditSink",
"parameters":[
{
"type":"string",
"paramType":"query",
"name":"pretty",
"description":"If 'true', then the output is pretty printed.",
"required":false,
"allowMultiple":false
},
{
"type":"v1.DeleteOptions",
"paramType":"body",
"name":"body",
"description":"",
"required":true,
"allowMultiple":false
},
{
"type":"integer",
"paramType":"query",
"name":"gracePeriodSeconds",
"description":"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.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"orphanDependents",
"description":"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.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"propagationPolicy",
"description":"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.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"dryRun",
"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed",
"description":"API at /apis/auditregistration.k8s.io/v1alpha1",
"operations":[
{
"type":"v1.WatchEvent",
"method":"GET",
"summary":"watch changes to an object of kind AuditSink. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.",
"nickname":"watchAuditSink",
"parameters":[
{
"type":"string",
"paramType":"query",
"name":"pretty",
"description":"If 'true', then the output is pretty printed.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"labelSelector",
"description":"A selector to restrict the list of returned objects by their labels. Defaults to everything.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"fieldSelector",
"description":"A selector to restrict the list of returned objects by their fields. Defaults to everything.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"includeUninitialized",
"description":"If true, partially initialized resources are included in the response.",
"required":false,
"allowMultiple":false
},
{
"type":"boolean",
"paramType":"query",
"name":"watch",
"description":"Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"resourceVersion",
"description":"When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.",
"required":false,
"allowMultiple":false
},
{
"type":"integer",
"paramType":"query",
"name":"timeoutSeconds",
"description":"Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.",
"required":false,
"allowMultiple":false
},
{
"type":"integer",
"paramType":"query",
"name":"limit",
"description":"limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.\n\nThe server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.",
"required":false,
"allowMultiple":false
},
{
"type":"string",
"paramType":"query",
"name":"continue",
"description":"The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.",
"description":"API at /apis/auditregistration.k8s.io/v1alpha1",
"operations":[
{
"type":"v1.APIResourceList",
"method":"GET",
"summary":"get available resources",
"nickname":"getAPIResources",
"parameters":[],
"produces":[
"application/json",
"application/yaml",
"application/vnd.kubernetes.protobuf"
],
"consumes":[
"application/json",
"application/yaml",
"application/vnd.kubernetes.protobuf"
]
}
]
}
],
"models":{
"v1alpha1.AuditSinkList":{
"id":"v1alpha1.AuditSinkList",
"description":"AuditSinkList is a list of AuditSink items.",
"required":[
"items"
],
"properties":{
"kind":{
"type":"string",
"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds"
},
"apiVersion":{
"type":"string",
"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources"
},
"metadata":{
"$ref":"v1.ListMeta"
},
"items":{
"type":"array",
"items":{
"$ref":"v1alpha1.AuditSink"
},
"description":"List of audit configurations."
}
}
},
"v1.ListMeta":{
"id":"v1.ListMeta",
"description":"ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.",
"properties":{
"selfLink":{
"type":"string",
"description":"selfLink is a URL representing this object. Populated by the system. Read-only."
},
"resourceVersion":{
"type":"string",
"description":"String that identifies the server's internal version of this object that can be used by clients to determine when objects have changed. Value must be treated as opaque by clients and passed unmodified back to the server. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency"
},
"continue":{
"type":"string",
"description":"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."
}
}
},
"v1alpha1.AuditSink":{
"id":"v1alpha1.AuditSink",
"description":"AuditSink represents a cluster level audit sink",
"properties":{
"kind":{
"type":"string",
"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds"
},
"apiVersion":{
"type":"string",
"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources"
},
"metadata":{
"$ref":"v1.ObjectMeta"
},
"spec":{
"$ref":"v1alpha1.AuditSinkSpec",
"description":"Spec defines the audit configuration spec"
}
}
},
"v1.ObjectMeta":{
"id":"v1.ObjectMeta",
"description":"ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.",
"properties":{
"name":{
"type":"string",
"description":"Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names"
},
"generateName":{
"type":"string",
"description":"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.\n\nIf this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header).\n\nApplied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#idempotency"
},
"namespace":{
"type":"string",
"description":"Namespace defines the space within each name must be unique. An empty namespace is equivalent to the \"default\" namespace, but \"default\" 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.\n\nMust be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces"
},
"selfLink":{
"type":"string",
"description":"SelfLink is a URL representing this object. Populated by the system. Read-only."
},
"uid":{
"type":"string",
"description":"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.\n\nPopulated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids"
},
"resourceVersion":{
"type":"string",
"description":"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.\n\nPopulated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency"
},
"generation":{
"type":"integer",
"format":"int64",
"description":"A sequence number representing a specific generation of the desired state. Populated by the system. Read-only."
},
"creationTimestamp":{
"type":"string",
"description":"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.\n\nPopulated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata"
},
"deletionTimestamp":{
"type":"string",
"description":"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.\n\nPopulated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata"
},
"deletionGracePeriodSeconds":{
"type":"integer",
"format":"int64",
"description":"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."
},
"labels":{
"type":"object",
"description":"Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels"
},
"annotations":{
"type":"object",
"description":"Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations"
},
"ownerReferences":{
"type":"array",
"items":{
"$ref":"v1.OwnerReference"
},
"description":"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."
},
"initializers":{
"$ref":"v1.Initializers",
"description":"An initializer is a controller which enforces some system invariant at object creation time. This field is a list of initializers that have not yet acted on this object. If nil or empty, this object has been completely initialized. Otherwise, the object is considered uninitialized and is hidden (in list/watch and get calls) from clients that haven't explicitly asked to observe uninitialized objects.\n\nWhen an object is created, the system will populate this list with the current set of initializers. Only privileged users may set or modify this list. Once it is empty, it may not be modified further by any user."
},
"finalizers":{
"type":"array",
"items":{
"type":"string"
},
"description":"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."
},
"clusterName":{
"type":"string",
"description":"The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request."
}
}
},
"v1.OwnerReference":{
"id":"v1.OwnerReference",
"description":"OwnerReference contains enough information to let you identify an owning object. Currently, an owning object must be in the same namespace, so there is no namespace field.",
"required":[
"apiVersion",
"kind",
"name",
"uid"
],
"properties":{
"apiVersion":{
"type":"string",
"description":"API version of the referent."
},
"kind":{
"type":"string",
"description":"Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds"
},
"name":{
"type":"string",
"description":"Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names"
},
"uid":{
"type":"string",
"description":"UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids"
},
"controller":{
"type":"boolean",
"description":"If true, this reference points to the managing controller."
},
"blockOwnerDeletion":{
"type":"boolean",
"description":"If true, AND if the owner has the \"foregroundDeletion\" finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. Defaults to false. To set this field, a user needs \"delete\" permission of the owner, otherwise 422 (Unprocessable Entity) will be returned."
}
}
},
"v1.Initializers":{
"id":"v1.Initializers",
"description":"Initializers tracks the progress of initialization.",
"required":[
"pending"
],
"properties":{
"pending":{
"type":"array",
"items":{
"$ref":"v1.Initializer"
},
"description":"Pending is a list of initializers that must execute in order before this object is visible. When the last pending initializer is removed, and no failing result is set, the initializers struct will be set to nil and the object is considered as initialized and visible to all clients."
},
"result":{
"$ref":"v1.Status",
"description":"If result is set with the Failure field, the object will be persisted to storage and then deleted, ensuring that other clients can observe the deletion."
}
}
},
"v1.Initializer":{
"id":"v1.Initializer",
"description":"Initializer is information about an initializer that has not yet completed.",
"required":[
"name"
],
"properties":{
"name":{
"type":"string",
"description":"name of the process that is responsible for initializing this object."
}
}
},
"v1.Status":{
"id":"v1.Status",
"description":"Status is a return value for calls that don't return other objects.",
"properties":{
"kind":{
"type":"string",
"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds"
},
"apiVersion":{
"type":"string",
"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources"
},
"metadata":{
"$ref":"v1.ListMeta",
"description":"Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds"
},
"status":{
"type":"string",
"description":"Status of the operation. One of: \"Success\" or \"Failure\". More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status"
},
"message":{
"type":"string",
"description":"A human-readable description of the status of this operation."
},
"reason":{
"type":"string",
"description":"A machine-readable description of why this operation is in the \"Failure\" status. If this value is empty there is no information available. A Reason clarifies an HTTP status code but does not override it."
},
"details":{
"$ref":"v1.StatusDetails",
"description":"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."
},
"code":{
"type":"integer",
"format":"int32",
"description":"Suggested HTTP return code for this status, 0 if not set."
}
}
},
"v1.StatusDetails":{
"id":"v1.StatusDetails",
"description":"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.",
"properties":{
"name":{
"type":"string",
"description":"The name attribute of the resource associated with the status StatusReason (when there is a single name which can be described)."
},
"group":{
"type":"string",
"description":"The group attribute of the resource associated with the status StatusReason."
},
"kind":{
"type":"string",
"description":"The kind attribute of the resource associated with the status StatusReason. On some operations may differ from the requested resource Kind. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds"
},
"uid":{
"type":"string",
"description":"UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids"
},
"causes":{
"type":"array",
"items":{
"$ref":"v1.StatusCause"
},
"description":"The Causes array includes more details associated with the StatusReason failure. Not all StatusReasons may provide detailed causes."
},
"retryAfterSeconds":{
"type":"integer",
"format":"int32",
"description":"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."
}
}
},
"v1.StatusCause":{
"id":"v1.StatusCause",
"description":"StatusCause provides more information about an api.Status failure, including cases when multiple errors are encountered.",
"properties":{
"reason":{
"type":"string",
"description":"A machine-readable description of the cause of the error. If this value is empty there is no information available."
},
"message":{
"type":"string",
"description":"A human-readable description of the cause of the error. This field may be presented as-is to a reader."
},
"field":{
"type":"string",
"description":"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.\n\nExamples:\n\"name\" - the field \"name\" on the current resource\n\"items[0].name\" - the field \"name\" on the first array entry in \"items\""
}
}
},
"v1alpha1.AuditSinkSpec":{
"id":"v1alpha1.AuditSinkSpec",
"description":"AuditSinkSpec holds the spec for the audit sink",
"required":[
"policy",
"webhook"
],
"properties":{
"policy":{
"$ref":"v1alpha1.Policy",
"description":"Policy defines the policy for selecting which events should be sent to the webhook required"
},
"webhook":{
"$ref":"v1alpha1.Webhook",
"description":"Webhook to send events required"
}
}
},
"v1alpha1.Policy":{
"id":"v1alpha1.Policy",
"description":"Policy defines the configuration of how audit events are logged",
"required":[
"level",
"stages"
],
"properties":{
"level":{
"type":"string",
"description":"The Level that all requests are recorded at. available options: None, Metadata, Request, RequestResponse required"
},
"stages":{
"type":"array",
"items":{
"$ref":"v1alpha1.Stage"
},
"description":"Stages is a list of stages for which events are created."
}
}
},
"v1alpha1.Stage":{
"id":"v1alpha1.Stage",
"properties":{}
},
"v1alpha1.Webhook":{
"id":"v1alpha1.Webhook",
"description":"Webhook holds the configuration of the webhook",
"required":[
"clientConfig"
],
"properties":{
"throttle":{
"$ref":"v1alpha1.WebhookThrottleConfig",
"description":"Throttle holds the options for throttling the webhook"
},
"clientConfig":{
"$ref":"v1alpha1.WebhookClientConfig",
"description":"ClientConfig holds the connection parameters for the webhook required"
}
}
},
"v1alpha1.WebhookThrottleConfig":{
"id":"v1alpha1.WebhookThrottleConfig",
"description":"WebhookThrottleConfig holds the configuration for throttling events",
"properties":{
"qps":{
"type":"integer",
"format":"int64",
"description":"ThrottleQPS maximum number of batches per second default 10 QPS"
},
"burst":{
"type":"integer",
"format":"int64",
"description":"ThrottleBurst is the maximum number of events sent at the same moment default 15 QPS"
}
}
},
"v1alpha1.WebhookClientConfig":{
"id":"v1alpha1.WebhookClientConfig",
"description":"WebhookClientConfig contains the information to make a connection with the webhook",
"required":[
"service",
"caBundle"
],
"properties":{
"url":{
"type":"string",
"description":"`url` gives the location of the webhook, in standard URL form (`[scheme://]host:port/path`). Exactly one of `url` or `service` must be specified.\n\nThe `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.\n\nPlease 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.\n\nThe scheme must be \"https\"; the URL must begin with \"https://\".\n\nA 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.\n\nAttempting to use a user or basic auth e.g. \"user:password@\" is not allowed. Fragments (\"#...\") and query parameters (\"?...\") are not allowed, either."
},
"service":{
"$ref":"v1alpha1.ServiceReference",
"description":"`service` is a reference to the service for this webhook. Either `service` or `url` must be specified.\n\nIf the webhook is running within the cluster, then you should use `service`.\n\nPort 443 will be used if it is open, otherwise it is an error."
},
"caBundle":{
"type":"string",
"description":"`caBundle` is a PEM encoded CA bundle which will be used to validate the webhook's server certificate. defaults to the apiservers CA bundle for the endpoint type"
}
}
},
"v1alpha1.ServiceReference":{
"id":"v1alpha1.ServiceReference",
"description":"ServiceReference holds a reference to Service.legacy.k8s.io",
"required":[
"namespace",
"name"
],
"properties":{
"namespace":{
"type":"string",
"description":"`namespace` is the namespace of the service. Required"
},
"name":{
"type":"string",
"description":"`name` is the name of the service. Required"
},
"path":{
"type":"string",
"description":"`path` is an optional URL path which will be sent in any request to this service."
}
}
},
"v1.WatchEvent":{
"id":"v1.WatchEvent",
"required":[
"type",
"object"
],
"properties":{
"type":{
"type":"string"
},
"object":{
"type":"string"
}
}
},
"v1.Patch":{
"id":"v1.Patch",
"description":"Patch is provided to give a concrete name and type to the Kubernetes PATCH request body.",
"properties":{}
},
"v1.DeleteOptions":{
"id":"v1.DeleteOptions",
"description":"DeleteOptions may be provided when deleting an API object.",
"properties":{
"kind":{
"type":"string",
"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds"
},
"apiVersion":{
"type":"string",
"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources"
},
"gracePeriodSeconds":{
"type":"integer",
"format":"int64",
"description":"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."
},
"preconditions":{
"$ref":"v1.Preconditions",
"description":"Must be fulfilled before a deletion is carried out. If not possible, a 409 Conflict status will be returned."
},
"orphanDependents":{
"type":"boolean",
"description":"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."
},
"propagationPolicy":{
"$ref":"v1.DeletionPropagation",
"description":"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."
},
"dryRun":{
"type":"array",
"items":{
"type":"string"
},
"description":"When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed"
}
}
},
"v1.Preconditions":{
"id":"v1.Preconditions",
"description":"Preconditions must be fulfilled before an operation (update, delete, etc.) is carried out.",
"properties":{
"uid":{
"$ref":"types.UID",
"description":"Specifies the target UID."
}
}
},
"types.UID":{
"id":"types.UID",
"properties":{}
},
"v1.DeletionPropagation":{
"id":"v1.DeletionPropagation",
"properties":{}
},
"v1.APIResourceList":{
"id":"v1.APIResourceList",
"description":"APIResourceList is a list of APIResource, it is used to expose the name of the resources supported in a specific group and version, and if the resource is namespaced.",
"required":[
"groupVersion",
"resources"
],
"properties":{
"kind":{
"type":"string",
"description":"Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds"
},
"apiVersion":{
"type":"string",
"description":"APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources"
},
"groupVersion":{
"type":"string",
"description":"groupVersion is the group and version this APIResourceList is for."
},
"resources":{
"type":"array",
"items":{
"$ref":"v1.APIResource"
},
"description":"resources contains the name of the resources and if they are namespaced."
}
}
},
"v1.APIResource":{
"id":"v1.APIResource",
"description":"APIResource specifies the name of a resource and whether it is namespaced.",
"required":[
"name",
"singularName",
"namespaced",
"kind",
"verbs"
],
"properties":{
"name":{
"type":"string",
"description":"name is the plural name of the resource."
},
"singularName":{
"type":"string",
"description":"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."
},
"namespaced":{
"type":"boolean",
"description":"namespaced indicates if a resource is namespaced or not."
},
"group":{
"type":"string",
"description":"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\"."
},
"version":{
"type":"string",
"description":"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's group)\"."
},
"kind":{
"type":"string",
"description":"kind is the kind for the resource (e.g. 'Foo' is the kind for a resource 'foo')"
},
"verbs":{
"type":"array",
"items":{
"type":"string"
},
"description":"verbs is a list of supported kube verbs (this includes get, list, watch, create, update, patch, delete, deletecollection, and proxy)"
},
"shortNames":{
"type":"array",
"items":{
"type":"string"
},
"description":"shortNames is a list of suggested short names of the resource."
},
"categories":{
"type":"array",
"items":{
"type":"string"
},
"description":"categories is a list of the grouped resources this resource belongs to (e.g. 'all')"
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">A selector to restrict the list of returned objects by their labels. Defaults to everything.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">A selector to restrict the list of returned objects by their fields. Defaults to everything.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">limit is a maximum number of responses to return for a list call. If more items exist, the server will set the <code>continue</code> field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
</p><pclass="tableblock">The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".
</p><pclass="tableblock">This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">A selector to restrict the list of returned objects by their labels. Defaults to everything.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">A selector to restrict the list of returned objects by their fields. Defaults to everything.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">limit is a maximum number of responses to return for a list call. If more items exist, the server will set the <code>continue</code> field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
</p><pclass="tableblock">The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".
</p><pclass="tableblock">This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">If IncludeUninitialized is specified, the object may be returned without completing initialization.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Should this value be exported. Export strips fields that a user can not specify.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Should the export be exact. Exact export maintains cluster-specific fields like <em>Namespace</em>.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">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.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">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.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">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: <em>Orphan</em> - orphan the dependents; <em>Background</em> - allow the garbage collector to delete the dependents in the background; <em>Foreground</em> - a cascading policy that deletes all dependents in the foreground.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</p></td>
<h3id="_watch_individual_changes_to_a_list_of_auditsink_deprecated_use_the_em_watch_em_parameter_with_a_list_operation_instead">watch individual changes to a list of AuditSink. deprecated: use the <em>watch</em> parameter with a list operation instead.</h3>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">A selector to restrict the list of returned objects by their labels. Defaults to everything.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">A selector to restrict the list of returned objects by their fields. Defaults to everything.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">limit is a maximum number of responses to return for a list call. If more items exist, the server will set the <code>continue</code> field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
</p><pclass="tableblock">The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".
</p><pclass="tableblock">This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</p></td>
<h3id="_watch_changes_to_an_object_of_kind_auditsink_deprecated_use_the_em_watch_em_parameter_with_a_list_operation_instead_filtered_to_a_single_item_with_the_em_fieldselector_em_parameter">watch changes to an object of kind AuditSink. deprecated: use the <em>watch</em> parameter with a list operation instead, filtered to a single item with the <em>fieldSelector</em> parameter.</h3>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">A selector to restrict the list of returned objects by their labels. Defaults to everything.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">A selector to restrict the list of returned objects by their fields. Defaults to everything.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">limit is a maximum number of responses to return for a list call. If more items exist, the server will set the <code>continue</code> field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
</p><pclass="tableblock">The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key".
</p><pclass="tableblock">This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</p></td>
"":"Webhook holds the configuration of the webhook",
"throttle":"Throttle holds the options for throttling the webhook",
"clientConfig":"ClientConfig holds the connection parameters for the webhook required",
}
func(Webhook)SwaggerDoc()map[string]string{
returnmap_Webhook
}
varmap_WebhookClientConfig=map[string]string{
"":"WebhookClientConfig contains the information to make a connection with the webhook",
"url":"`url` gives the location of the webhook, in standard URL form (`[scheme://]host:port/path`). Exactly one of `url` or `service` must be specified.\n\nThe `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.\n\nPlease 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.\n\nThe scheme must be \"https\"; the URL must begin with \"https://\".\n\nA 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.\n\nAttempting to use a user or basic auth e.g. \"user:password@\" is not allowed. Fragments (\"#...\") and query parameters (\"?...\") are not allowed, either.",
"service":"`service` is a reference to the service for this webhook. Either `service` or `url` must be specified.\n\nIf the webhook is running within the cluster, then you should use `service`.\n\nPort 443 will be used if it is open, otherwise it is an error.",
"caBundle":"`caBundle` is a PEM encoded CA bundle which will be used to validate the webhook's server certificate. defaults to the apiservers CA bundle for the endpoint type",
